[Bast-commits] r7776 - DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual

triode at dev.catalyst.perl.org triode at dev.catalyst.perl.org
Fri Oct 9 20:32:04 GMT 2009


Author: triode
Date: 2009-10-09 20:32:04 +0000 (Fri, 09 Oct 2009)
New Revision: 7776

Modified:
   DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Troubleshooting.pod
Log:
added troubleshooting case of excessive memory allocation involving TEXT/BLOB/etc
columns and large LongReadLen


Modified: DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Troubleshooting.pod
===================================================================
--- DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Troubleshooting.pod	2009-10-09 09:04:50 UTC (rev 7775)
+++ DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Troubleshooting.pod	2009-10-09 20:32:04 UTC (rev 7776)
@@ -156,5 +156,16 @@
 L<https://bugzilla.redhat.com/show_bug.cgi?id=460308> and
 L<http://rhn.redhat.com/errata/RHBA-2008-0876.html>
 
+=head2 Excessive Memory Allocation with TEXT/BLOB/etc. Columns and Large LongReadLen
+
+It has been observed, using L<DBD::ODBC>, that a creating a L<DBIx::Class::Row> 
+object which includes a column of data type TEXT/BLOB/etc. will allocate 
+LongReadLen bytes.  This allocation does not leak, but if LongReadLen 
+is large in size, and many such row objects are created, e.g. as the 
+output of a ResultSet query, the memory footprint of the Perl interpreter 
+can grow very large.
+
+The solution is to use the smallest practical value for LongReadLen.
+
 =cut
 




More information about the Bast-commits mailing list