• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Creating new object results in an out of memory error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Creating new object results in an out of memory error


  • Subject: Re: Creating new object results in an out of memory error
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 18 Sep 2007 20:19:07 -0700

This, or a related issue can be triggered by firing a large (many members) back pointing relationship. Sometimes for efficiency, these are best managed manually and not modeled as a relationship.

Chuck


On Sep 18, 2007, at 2:57 PM, David Holt wrote:

Well, I figured out the problem.

In Practical WebObjects on page 44 Chuck and Sacha recommend as one possibility moving the LOB data into a related entity. They say that "This allows you to avoid faulting in the LOB until you need it". When I fetch my entity, the LOB table is included, not faulted as I was expecting. This is why I am running out of memory.

It turns out that a derived attribute that I was using to search the LOB combined with other fields in the main artifact (using the coalesce function) caused the LOB to be loaded into memory behind the scenes with each record. Not good for performance. I am going to implement the search as individual search fields instead. The Google simulation will have to wait for another day!

David

On 18-Sep-07, at 1:39 PM, David Holt wrote:

Hi,

I have recently solved an out of memory problem in a list page by using a batching display group that just fetches one page worth of records at a time.

Now I find that creating an object from that page is once again trying to fetch every record in the data table prior to allowing me to save changes. Is there some way around this? I understand that EOF wants to ensure that I haven't already created that object, but is it necessary to load the entire table into memory? Thanks,

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


This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net


This email sent to email@hidden


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






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


  • Follow-Ups:
    • Re: Creating new object results in an out of memory error
      • From: Alexander Spohr <email@hidden>
References: 
 >Creating new object results in an out of memory error (From: David Holt <email@hidden>)
 >Re: Creating new object results in an out of memory error (From: David Holt <email@hidden>)

  • Prev by Date: Re: Apple Please Update java Plot.framework
  • Next by Date: Re: Apple Please Update java Plot.framework / Think Different
  • Previous by thread: Re: Creating new object results in an out of memory error
  • Next by thread: Re: Creating new object results in an out of memory error
  • Index(es):
    • Date
    • Thread