Re: Batch faulting
Re: Batch faulting
- Subject: Re: Batch faulting
- From: Peter Vandoros <email@hidden>
- Date: Tue, 03 Jul 2007 08:59:01 +1000
Thanks for your responses.
I already knew about the query size limit Julius mentioned and the
possibly unneeded faulting of objects that might not be used causing my
app to use more memory than needed. I just wanted to see if there were
any corner case type issues that i wasn't aware of.
Thanks for all your help.
Peter
Ken Anderson wrote:
On Jul 2, 2007, at 4:15 AM, Peter Vandoros wrote:
Hi list,
We are in the "optimize" process with one of our apps and i have a
few questions regarding batch faulting/fetching objects:
Is there any reason why the limit batch size for batch faulting is
100 (well at least this is what we have found)?
It depends - if your app server is very close to your DB (so network
performance doesn't matter), your objects are reasonable size, and you
don't mind filling memory with a lot of objects, no.
Why isn't batch faulting enabled by default if it seemingly should be
used in all cases? i.e. don't we want to always batch fetch objects
instead of fetching them one by one when the fault is fired?
See above.
Does anyone see any possible issues with specifying all entities to
be batch fetched with a batch size of 100 (or more if possible)?
The same as above. If you had records with 1 GB of blob data, I'd
doubt you'd want to batch fetch 100 of them.
Also, consider this pattern. You have entity X with 3000 instances in
memory. You allow the user to select them from a list, and when they
select one, a to-one fault is fired. It's possible that users will
not pick instances 1,2,3 - but instance 12, instance 436, and instance
698. If you have batch faulting turned on with 100 objects, you'll
likely fetch 300 when you only want 3.
Ken
We are using WO 5.2.4.
Thanks
--
Peter Vandoros
Software Engineer
Etech Group Pty Ltd
Level 3/21 Victoria St
Melbourne VIC 3000
Australia
Ph: +61 3 9639 9677
Fax: +61 3 9639 9577
----------------------------------
IMPORTANT: This e-mail message and any attachments are confidential
and may be privileged. If received in error, please reply to this
message and destroy all copies and any attachments. You should check
this message and any attachments for viruses or defects. Our
liability is limited to resupplying any affected message or
attachments. For more information about Etech Group, please visit us
at http://www.etechgroup.com.au.
_______________________________________________
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
_______________________________________________
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
--
Peter Vandoros
Software Engineer
Etech Group Pty Ltd
Level 3/21 Victoria St
Melbourne VIC 3000
Australia
Ph: +61 3 9639 9677
Fax: +61 3 9639 9577
----------------------------------
IMPORTANT: This e-mail message and any attachments are confidential and
may be privileged. If received in error, please reply to this message
and destroy all copies and any attachments. You should check this
message and any attachments for viruses or defects. Our liability is
limited to resupplying any affected message or attachments. For more
information about Etech Group, please visit us at
http://www.etechgroup.com.au.
_______________________________________________
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