My guesses:
Your application has bad sync locking between some threads, which is
causing one thread to block the others.
Your application has bad database access code, which allows one thread
to block others while waiting on the DB.
Your application is disk bound, and the single long process is
On Oct 16, 2008, at 9:05 PM, Matthew Laird wrote:
Caldarale, Charles R wrote:
"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 Fri, Oct 17, 2008 at 3:05 AM, Matthew Laird <[EMAIL PROTECTED]> wrote:
>
> Caldarale, Charles R wrote:
>
>> "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
tthew Laird [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat not using multiple cores
But of course I'm not a Java or JVM expert and have no idea
what kind of interlinks can exist between different client
connections.
Again - get a thread dump when at 100% on one core and 0% on the oth
> From: Matthew Laird [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat not using multiple cores
>
> But of course I'm not a Java or JVM expert and have no idea
> what kind of interlinks can exist between different client
> connections.
Again - get a thread dump when at 100
Caldarale, Charles R wrote:
"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 sy
ey
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
> 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 i
This will be a helpful document:
http://java.sun.com/docs/hotspot/gc5.0/ergo5.html
Brantley
Matthew Laird wrote:
We're pulling our hair out with a Tomcat issue.
We have an in-house application running on Tomcat 5.5 with Sun JDK 1.6.
The machine is an x86 dual-CPU, quad core (8 cores total) w
I think that this is a garbage collection issue.
Enable the garbage collection output to see if that's the case (the
"-verbose:gc" flag) . I struggled with this myself just a month ago and
ended up learning more about Java GC than I ever wanted to know. The
gist of it is that when the JVM ru
> From: Matthew Laird [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat not using multiple cores
>
> From Tomcat, as far as I understand you can only do 2GB per Tomcat
> instance. Please correct me if I'm wrong.
Not true. The limitation is due to the OS, not the JVM and certa
From the OS, no.
From Tomcat, as far as I understand you can only do 2GB per Tomcat
instance. Please correct me if I'm wrong.
Jim Cox wrote:
On Thu, Oct 16, 2008 at 10:30 PM, Matthew Laird <[EMAIL PROTECTED]> wrote:
[...lines snipped...]
We have an in-house application running on Tomcat 5.5
On Thu, Oct 16, 2008 at 10:30 PM, Matthew Laird <[EMAIL PROTECTED]> wrote:
[...lines snipped...]
> We have an in-house application running on Tomcat 5.5 with Sun JDK 1.6.
> The machine is an x86 dual-CPU, quad core (8 cores total) with 16GB of
> RAM. We're running OpenSuSE 10.2, 32-bit. Java mem
Hello Matthew,
Without wanting to advertise own product, I think moskito can help you
a lot here. It was specially designed to detect
cpu eaters among call trees. Feel free to contact me of list if you
want to give it a try ;-)
http://moskito.anotheria.net/moskitodemo/mui/mskShowAllProducers
reg
> From: Matthew Laird [mailto:[EMAIL PROTECTED]
> Subject: Tomcat not using multiple cores
>
> Unfortunately what then occurs is all other threads suddenly become
> unusably slow. The entire web application grinds to a halt until this
> thread that's running hot completes.
We've run Tomcat on 32
15 matches
Mail list logo
