Re: load testing
Re: load testing
- Subject: Re: load testing
- From: Mike Schrag <email@hidden>
- Date: Tue, 26 Jul 2005 13:36:44 -0400
Yes, this seems odd to me too. Was your load testing resulting in more concurrent saveChanges() calls than the app would really encounter? I've never timed this with and without the shared EC. It could be that nobody else has either. Perhaps I can get a huge performance boost!
Interestingly, these were all "read-only" load tests, so zero calls to saveChanges. Now it WAS the case that the load tests behaviors were a little odd in that it was (in this particular test) 50 concurrent threads hitting a random sequence of 100 pages with zero pause between requests (i.e. effectively far more than 50 concurrent users since a "real user" would have at least a few seconds of pause between hits). If you are not using it then there is no need for it.
This is what I'm seeing also -- Haven't noticed any ill effects. 3) is there a better fix for whatever it is I am seeing with this lock contention, or if nobody is seeing this issue, I'll go back to the profiler drawing board and see if i can track down more specifically where the contention is coming from
I actually haven't had a chance to go back and diagnose this further, but I should have time later this week. ms |
_______________________________________________
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