Re: OutOfMemoryError: reading a large number of objects one by one

2007-05-16 Thread Derek Rendall
My patch seemed to scale well - it got to about (I think) 40 Meg or so then stabilized with only nominal growth from there. I did not test much higher than 100 K records as I did not need to. I guess the size will be related to how big each record is when represented as a data row * number of

Re: OutOfMemoryError: reading a large number of objects one by one

2007-05-15 Thread Andrus Adamchik
On May 15, 2007, at 12:47 AM, Tomi N/A wrote: Reduced the max number of objects to 1000. The result? A NPE at: for (MyClassC mcc : (ListMyClassC)mca.getToMyClassC().getToParentClass ().getMyClassCArray()) { Ok, so the cache size will have to be big enough to hold all

OutOfMemoryError: reading a large number of objects one by one

2007-05-14 Thread Tomi N/A
I'll try to be to the point. I need: - to stream data from potentially large tables - wan't the app to not use more than a couple of MB of RAM, as (theoretically) there shouldn't be a reason for it to need any more Using cayenne 1.2 something (no, switching to something a bit more modern is not

Re: OutOfMemoryError: reading a large number of objects one by one

2007-05-14 Thread Tomi N/A
2007/5/14, Andrus Adamchik [EMAIL PROTECTED]: On May 14, 2007, at 8:57 PM, Tomi N/A wrote: mca = (MyClassA) Util.getCommonContext().objectFromDataRow(SpisUtil.class, dr, false); This is the source of the memory leak. You may want to replace the context after processing an X number of rows.

Re: OutOfMemoryError: reading a large number of objects one by one

2007-05-14 Thread Tomi N/A
2007/5/14, Andrus Adamchik [EMAIL PROTECTED]: You may also try to reduce the Max Number of Objects for the DataDomain from the default 1 to something smaller. Also are you setting -Xmx to something small? You may want to start with the higher values, if only to be able to see the effect of