Dimple,
On 11/9/15 3:46 AM, dimple ranka wrote:
> Some help is really appreciated, atleast it will be good to hear if some
> one else is also facing slowness with the tomcat7 server.
>
> I did some more investigation here and as mentioned earlier saw the
> slowness with tomcat7 is more
On Mon, Nov 9, 2015 at 8:34 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Dimple,
>
> On 11/9/15 3:46 AM, dimple ranka wrote:
> > Some help is really appreciated, atleast it will be good to hear if some
> > one else is also facing slowness with the tomcat7 server.
> >
> > I did
Hi all,
Some help is really appreciated, atleast it will be good to hear if some
one else is also facing slowness with the tomcat7 server.
I did some more investigation here and as mentioned earlier saw the
slowness with tomcat7 is more reproducible when there are some
cryptographic signature
Looks like attachments are not allowed so only sharing the contents of
threadDump3.out
2015-11-04 22:55:58
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode):
"http-nio-8443-exec-147" daemon prio=10 tid=0x7f5c1c005000 nid=0x6241
runnable [0x7f5bd30ef000]
Hi Chris,
I captured 3 threadumps with the below requests/second when the server is
already slow. We were using BIO before and had observed slowness even with
that. We switched to using NIO since it seemed a recommendation for
production environment.
Dimple,
On 11/3/15 11:24 PM, dimple ranka wrote:
> Also forgot to mention that setting maxKeepAliveRequests to -1 did not
> help. As expected from the connector documentation the default value for
> this attribute is 100 and we have a 60 user test set up.
>
> On Wed, Nov 4, 2015 at 8:18 AM,
On 03/11/2015 06:17, dimple ranka wrote:
> ##
> On tomcat7 number of requests fullfilled per second
> ##
> * RUN1 ** ==> ** 38128.97704918033 runs/sec*
> *RUN2 ==> ** 19040.35947712418 runs/sec*
> *RUN3
Hi Mark,
The test client is running on another machine.
The server side test code is written using jersey 1.17.
Will try out with playing with maxKeepAliveRequests.
My only concern is that if jmeter is doing spoofy things then why it doesnt
show up on tomcat6.
Thanks,
Dimple
On Tue, Nov 3,
Hi Mark,
Another observation to be noted here is that system CPU usage shoots up for
subsequent runs, especially for later runs.
We have been looking into this issue for couple of weeks now and it is
clear in the same environment with the same setup it doesn't reproduce on
tomcat6. The moment we
Also forgot to mention that setting maxKeepAliveRequests to -1 did not
help. As expected from the connector documentation the default value for
this attribute is 100 and we have a 60 user test set up.
On Wed, Nov 4, 2015 at 8:18 AM, dimple ranka wrote:
> Hi Mark,
>
>
Hi all,
I am doing some performance data collection on tomcat7 on a 8 processor
high end machine with CentOS release 6.7 (Final) operating system and i am
observing slowness with subsequent runs of the same jmeter test. Here are
the version and specfication details followed by the endpoint source
11 matches
Mail list logo