-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/23/13 11:11 PM, Chirag Dewan wrote:
Chris,
The profiler shows very high CPU utilization in Tomcat threads.
As I said before a lot of time was spent during the
ResponseFacade.setContentType() method call. That doesn't tell the
On 24/05/2013 15:54, Christopher Schultz wrote:
Chirag,
On 5/23/13 11:11 PM, Chirag Dewan wrote:
Chris,
The profiler shows very high CPU utilization in Tomcat threads.
As I said before a lot of time was spent during the
ResponseFacade.setContentType() method call. That doesn't tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/23/13 11:11 PM, Chirag Dewan wrote:
As I said before a lot of time was spent during the
ResponseFacade.setContentType() method call. That doesn't tell the
whole story but more or less the high utilization is mainly in the
tomcat
Chris,
Sorry I should have posted the data first. I probably missed the most important
part of a load test. I will do it shortly.
And I am not using Jmeter now,I am using an http client for load test. I am
testing it on Solaris x86 server 64bit JVM. And i have collected the samples
for Tomcat
On 24.05.2013 17:54, Christopher Schultz wrote:
Top reported that Tomcat was taking somewhere between 550-600% CPU.
(This is a 4-core hyperthreaded CPU so I have 8 logical cores. 'ab'
was taking about 100% CPU so I think 600% CPU means it was roughly
pegging 6 of my logical cores. Roughly 30%
to Tomcat 7 under these circumstances.
Thanks.
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, 22 May 2013 7:30 PM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to Tomcat
Users Listusers@tomcat.apache.org
Sent: Wednesday, 22 May 2013 7:30 PM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to Tomcat
7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/21/13 11:03 PM, Chirag Dewan wrote:
I was monitoring the CPU utilization
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 5/23/13 7:40 AM, David kerber wrote:
On 5/23/2013 4:53 AM, Chirag Dewan wrote:
Hi All,
I tested Tomcat 7.0.40 with Solaris x86. It gave better CPU
performance than Tomcat 7.0.30 . It was able to handle 70K
requests at 45% CPU
Chris,
With c=1 it is 70k req/sec and with c=2 it is 35k in both i.e the total req/sec
cannot be scaled beyond 70k. With Tomcat 6 it is 60k in both clients i.e total
of 120k.
I do not expect more than 75k req/sec being served by Tomcat 7,but its the
benchmark set by Tomcat 6 which I can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/23/13 1:21 PM, Chirag Dewan wrote:
With c=1 it is 70k req/sec and with c=2 it is 35k in both i.e the
total req/sec cannot be scaled beyond 70k. With Tomcat 6 it is 60k
in both clients i.e total of 120k.
I do not expect more than
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, 24 May 2013 3:24 AM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to Tomcat
7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/23/13 1:21 PM, Chirag Dewan wrote:
With c=1 it is 70k req/sec
On 22/05/2013 04:03, Chirag Dewan wrote:
My Jprofiler stack trace on Solaris is a lot different. As far as
I have observed,for Tomcat 7 the stack Trace leads me to
ResponseFacade.setContentType,which was not the behaviour in
Tomcat 6. Can that be a bottleneck? Or is there something platform
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/21/13 11:03 PM, Chirag Dewan wrote:
I was monitoring the CPU utilization specifically. I can
compromise on 1 less transactions/sec,but 80-90% utilization is
not good.
While it's nice to reduce resource utilization as much as
from Embedded Tomcat 6 to Tomcat
7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/21/13 11:03 PM, Chirag Dewan wrote:
I was monitoring the CPU utilization specifically. I can
compromise on 1 less transactions/sec,but 80-90% utilization is
not good.
While it's nice
?
Thanks.
From: Chirag Dewan chirag.dewa...@yahoo.in
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, 20 May 2013 8:08 PM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to Tomcat
7
I ran my test client on Hello World example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/20/13 10:38 AM, Chirag Dewan wrote:
I ran my test client on Hello World example servlet on Tomcat
7.0.30. It was 12K req/sec with 80% CPU utilization.
The same test case on tomcat 6.0.18 gave me similar req/sec but
CPU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/21/13 6:08 AM, Chirag Dewan wrote:
It might be weird but its confusing me a lot.
I used HttpClient 4.2.1 for Tomcat 6.0.18 and I used the same
client with Tomcat 7.0.30,causing the CPU utilization and reduced
trans/sec.
.
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, 21 May 2013 9:08 PM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to Tomcat
7
-BEGIN PGP SIGNED MESSAGE-
Hash
From: Chirag Dewan [mailto:chirag.dewa...@yahoo.in]
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to
Tomcat 7
Well I tested a sample html page with Tomcat 6.0.18 and 7.0.30 on Solaris x86
server. The req/sec were almost the same for both, but CPU utilization
Yes. With same JVM on both Solaris and Linux i.e Java 1.6.39. It is 64 bit
version.
Thanks.
Sent from Yahoo! Mail on Android
throughput?
Thanks.
From: Chirag Dewan chirag.dewa...@yahoo.in
To: users@tomcat.apache.org users@tomcat.apache.org; ma...@apache.org
ma...@apache.org
Sent: Friday, 17 May 2013 6:30 PM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6
On 20/05/2013 06:59, Chirag Dewan wrote:
Hi,
I have profiled the application using JProfiler,and it seems to me
that its my servlet which is taking the majority of time.
Though the time is in mili seconds,but I guess since the servlet is
code is same as with Tomcat 6.0.18 is it the
: Monday, 20 May 2013 1:48 PM
Subject: Re: Performance Issue while upgrading from Embedded Tomcat 6 to Tomcat
7
On 20/05/2013 06:59, Chirag Dewan wrote:
Hi,
I have profiled the application using JProfiler,and it seems to me
that its my servlet which is taking the majority of time.
Though
Hi All,
I have upgraded my application from Embedded Tomcat 6 to Embedded Tomcat 7.
With Tomcat 6, I was getting around 7 Transactions per sec with a simple
HTTP service,which sets the HTTPResponse and returns it.
Now with Tomcat 7,I am getting 54000 transactions per sec. Going through
On 17/05/2013 11:51, Chirag Dewan wrote:
Hi All,
I have upgraded my application from Embedded Tomcat 6 to Embedded
Tomcat 7. With Tomcat 6, I was getting around 7 Transactions per
sec with a simple HTTP service,which sets the HTTPResponse and
returns it.
Now with Tomcat 7,I am
I am comparing tomcat 6.0.18 with tomcat 7.0.30.
Would adding NIO or APR connector help? Currently I am using default(BIO)
connector.
Thanks.
Sent from Yahoo! Mail on Android
Another important factor is the CPU utilization. Earlier for same trans/sec it
was 40% now its close to 80%.
And yes,the OS,JVM and memory setting are unchanged.
Thanks.
Sent from Yahoo! Mail on Android
On 17/05/2013 13:29, Chirag Dewan wrote:
Another important factor is the CPU utilization. Earlier for same trans/sec
it was 40% now its close to 80%.
I'd upgrade to the latest 7.0.39 but otherwise, definitely time for a
profiler.
If you want raw performance on kept-alive connections then BIO
I am running it on Solaris x86 server. I haven't even changed my code much.
Let me add a profiler,will post the results.
Thanks.
Sent from Yahoo! Mail on Android
29 matches
Mail list logo