Re: Understanding the PageCache Working
Re: Understanding the PageCache Working
- Subject: Re: Understanding the PageCache Working
- From: Paul Lynch <email@hidden>
- Date: Fri, 25 Aug 2006 18:23:44 +0100
Each entry in the page cache is the top level WOComponent for a page,
by context id. Checking out the references in your WOComponent will
tell you what objects are being retained. So any EOs held in
instance variables, etc.
Paul
On 25 Aug 2006, at 17:46, Kieran Kelleher wrote:
AFAIK, the page cache contains WOComponents and the template/wod.
The final HTML is generated each time the response is generated. If
you have memory expensive objects on a page, have them created via
lazy initialization and set the object to bull AFTER append to
response is complete. Then the memory expensive objects are no
longer referred to by the page WOComponent instance in the page cache.
Does that make sense?
Regards, Kieran
On Aug 25, 2006, at 10:39 AM, Ute Hoffmann wrote:
Hallo,
just a question for clarification again. In my app there are some
big pages (containing a lot of data and html). In the page cache,
will there be only saved a reference and the template or will the
html-page with complete content be saved or is it completely
different?
Follow up: If a database fetch was for a page that is still in the
pageCache of an application, is the ec of this database fetch
eligible for garbage collection (if it holds only the data for
this singe page) or will it stay around until the page it was
originally used for is out of the pageCache?
_______________________________________________
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