There are a number of things that can be done to resolve this.

1. Allow your application to use more memory by increasing the heap size.
     [This is good if you are running your app with too little heap space]

2. Make your application use less memory by qualifying your fetches more precisely.
     [May not be possible in some cases]

3. Make your application more efficient by using "Raw Row Fetching"
    [Uses less memory than "real" objects]
    [Makes your code database specific in some cases, but allows "real" fetch limits]
    [Can still make "real" enterprise objects from raw rows when needed]

On Mar 7, 2006, at 5:10 PM, Randy Wigginton wrote:

Hello,

My program loads a great deal of data from the database.  I process it, then attempt to “free” the memory.  My code looks vaguely like this:

For (all objects) {

EOEditingContext tmp = new EOEditingContext();

<load objects from tmp with a fetch specification>

 

tmp.invalidateAllObjects();

tmp = null;

System.gc();

}

 

Even with this, I’m running out of memory.  Any hints on making EO throw away everything it knows about?

 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:

This email sent to [EMAIL PROTECTED]

Robert Walker



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to