Re: 20 Second Delay on editingContext.saveChanges()
Re: 20 Second Delay on editingContext.saveChanges()
- Subject: Re: 20 Second Delay on editingContext.saveChanges()
- From: Chuck Hill <email@hidden>
- Date: Thu, 8 Jul 2010 12:20:07 -0700
On Jul 8, 2010, at 10:28 AM, Mark Ritchie wrote:
> On 8/Jul/2010, at 10:58 AM, Chuck Hill wrote:
>> Is the database content (not the schema) the same for both deployments? Could one have a very large number of back-pointing relationships that the other does not have? If so, I will suggest that you have a modelling issue. If not... puzzling.
>
> If this were the case, then there should be a select in the SQL log with a large number of records?
> Or perhaps many selects due to faulting or some such...
> Greg, what's the SQL log look like?
I think that without Anjo's change, even if the objects are already in memory it can be slow even for a few 10 of Ks of EOs. If they have to be fetched, it gets even worse.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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