load testing
load testing
- Subject: load testing
- From: Mike Schrag <email@hidden>
- Date: Thu, 21 Jul 2005 18:34:18 -0400
So I've been load testing my app w/ Apache JMeter while profiling it
with JProfiler, both really cool apps that are working really nicely
together -- just a public service announcement to start things off.
So single "user" things were great ... Then I tossed 50 concurrent
"users" at it and things didn't go so well. CPU usage was relatively
low, memory was no problem at all, so obviously I'm thinking lock
contention. So I attach JProfiler and sure enough my app is spending
a HUGE amount of time (like >30%) in sharedEditingContext.unlock().
Odd because I don't actually use shared editing context. So for
grins I added EOSharedEditingContext.setDefaultSharedEditingContext
(null) to the top of my app and performance was around 10x faster.
So my three part question:
1) does the original behavior sound odd? it sure SEEMS odd to me --
particularly since nobody else has mentioned this ... which leads me
to believe it's my fault ... which is historically a safe bet to make
when it comes to Me vs WO
2) what horrors will i bring upon my family by completely removing
the shared editing context ... my tests have not revealed a problem
yet, but i don't want to set myself up for trouble
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
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