Re: refreshes refetched objects: effects on performance?
Re: refreshes refetched objects: effects on performance?
- Subject: Re: refreshes refetched objects: effects on performance?
- From: Chuck Hill <email@hidden>
- Date: Thu, 04 Mar 2004 14:38:28 -0800
Define significant. Think about what it has to do:
1. Pull back all the rows. No change here as it has to do this even for a
non-refreshing fetch.
2. Check timestamps on snapshot for unfired faults. No need to do this if
refetching so maybe a little time made up here.
3. Refresh a whack of previously fetched objects. It would not do this
otherwise so you will lose time here.
4. Send ObjectChangedInObjectStore to all EC so they also can refresh the
object. This is also not done otherwise and might take a while depending on
how many editing contexts also hold these objects.
I think...
Chuck
At 02:50 PM 04/03/2004 -0600, Jonathan Rochkind wrote:
>When fetching a lot of objects, will setting the fetch spec to
>refreshesRefetchedObjects==true have a significant effect at making
>the fetch even slower? [We all know that fetches of lots of objects
>are already slower than we wish they were].
>
>Does anyone have any experience or evidence on this issue?
>
>I have a complicated fetch which returns a lot of objects, and the
>whole process is too slow, I'm trying to improve it. I'm wondering
>about theeffect if any of refreshesRefetchedObjects.
>
>--Jonathan
>_______________________________________________
>webobjects-dev mailing list | email@hidden
>Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
>Do not post admin requests to the list. They will be ignored.
>
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.