RE: caching
RE: caching
- Subject: RE: caching
- From: Andrew Lindesay <email@hidden>
- Date: Thu, 12 May 2005 08:07:23 +1200
...I have a table containing well over 600.000 tuples. With a
WODisplayGroup on this table I get an out of memory error.
Hi Jan;
I tend to use a fetch-spec to load up heaps of raw-rows into memory.
These raw rows contain the primary key. As the user pages through the
data I turn the raw-rows (with the primary key in them) into full-blow
EO's and render them to the HTML page. This mechanism works very well.
Get in touch if you want me to point you at some code samples.
If you are producing a result set that is the product of those 600,000
tuples, you will need to use other approaches. In this circumstance, I
tend to use a similar approach, but I'll roll through the data set like
this:
ec.lock();
<fault some RR's to EO's>
<process the data>
ec.unlock()
<force garbage collect> (unfortunate)
Essentially it's the same, but not drive my the request-response cycle.
The storage of the resultant data-set is also an issue, but that can
be overcome using streaming to some suitable storage media.
Hope this helps.
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
+64-21-47-0929
_______________________________________________
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