This is the exact thing that makes me think that that's the problem. I
saw the exact same symptoms: No matter how many CPU's I threw at it and
no matter how I threaded my app, I was only consuming one CPU in total.
I know it sounds counter-intuitive, and I could easily be wrong (I'm no
JVM memory expert), but this is almost verbatim the exact same problem I
had, and it was solved with GC tuning.
I'm no gambler, but if I were I'd be willing bet that when he enables GC
verbose output that he'll see more and more time going to major collections.
Brantley
Caldarale, Charles R wrote:
From: Brantley Hobbs [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat not using multiple cores
I think that this is a garbage collection issue.
Extremely unlikely, since the OP has already stated:
"The only time I began to see the other cores actually start being used is when I
enabled multi-threaded GC. But that doesn't give much improvement since the threads
responding the web requests are still all on the same core."
The most likely cause is internal synchronization in the webapp or the database
it references.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
