Thank you for taking the time to help out Pierce,
I've been watching WOStats and it doesn't seem to be indicating
anything odd. I don't use sessions or component actions, so all that
stuff is blank.
As for the direct actions. I see numbers like minimum time 0.007,
average time of 0.084 and maximum time of 0.910. I see memory usage of
33,423,360 and free of 21,221,976. So that seems like it's getting
more memory than it needs. But I think I'll up the memory per instance
a bit just in case.
I think you are right that I need to find some program that can sample
a java process and let me see what's going on. I have a feeling it's
the only way I can figure out what might be dragging in the
application. I'll have a look at shark and see if that has the
capabilities I need.
Of course it could be that the site is just getting more traffic than
2 app servers can handle. I just REALLY hate fixing what could be
software problem with a hardware solution. At this point I just can't
tell if it's a software problem or just too much traffic.
Thanks for you time,
Eric
On 6/10/06, Pierce T. Wetter III <[EMAIL PROTECTED]> wrote:
>
> on Pool Size: 1
>
> I guess my question is where, outside of what I've already stated,
> should I start to look for my bottleneck? Are there some tools in WO
> or XServe that I haven't mentioned yet, that I should be looking at?
>
> I think I (and Robert Walker who has been assisting me with this
> project so far) have done a pretty good job with things so far. But I
> guess I've hit the edge of my knowledge because I can't seem to
> locate the problem I'm having.
Things I would try:
1. WOStats.
2. Whatever the java equivalent of "sample" is. (man sample)
That is, I'd run a stack sampler to see what all the threads are
doing in your app. That usually tells me what's going on better
then anything else. Shark works with Java so you can try that.
For instance, databases rarely are CPU bound, usually they are
I/O bound. So if your app instances are stuck waiting for data
from the database, the database machines could easily have 5%
CPU usage because they're waiting on the disk. In fact, low CPU
usage can actually be a sign of database _problems_..
Pierce
WOTip: Don't use load balancing in the adaptor. Use roundrobin.
More Tips: http://www.twinforces.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
