You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rafael Oliveira de Mattos <ra...@softplan.com.br> on 2015/12/17 21:09:50 UTC

troughput difference

Hello, 

I'm having different results in Tomcat performance using version 6.0.37 and 8.0.23. 

Using tomcat 6 we usually have 
5000 ~ rpm with a response time of 80ms 

Using tomcat 8 the max that we can get is 
2000 ~ rpm with a response time of 200ms 

We are using the same jdk version 1.7.0.80, a nd the same applications on both version, they are installed in the same machine and using APR, but not running at the same time. 
We tried to use the same configuration whenever possible. 

SO: Linux ubuntu 12.04 
JDK: 1.7.0.80 
Anything I should take look at it? 

Re: troughput difference

Posted by Rafael Oliveira de Mattos <ra...@softplan.com.br>.
Ok,

Sorry for taking so long to answer, we are using this versions in a production enviroment (one server, to just selected users).

So we solved our problem, we changed the jsp-api that tomcat uses, we are using the jsp-api 2.2 from glassfish (we are still studying the side effects from that change). After we profile, our thread dumps showed that 60% of the time of the request were spended in tag.service methods. At first we thought that the error was in our code, but we didnt change anything in the jsp's. So after searching for the problem, we find this bug report https://bz.apache.org/bugzilla/show_bug.cgi?id=57583. With the glassfish version we are faster then ever, but we afraid of the side effects this can have.







----- Mensagem original -----
De: "Christopher Schultz" <ch...@christopherschultz.net>
Para: "Tomcat Users List" <us...@tomcat.apache.org>
Enviadas: Quinta-feira, 24 de dezembro de 2015 15:28:49
Assunto: Re: troughput difference

Aurélien,

On 12/24/15 4:17 AM, Aurélien Terrestris wrote:
> probably this won't solve your problem but I notice that the random seems
> slow :
> Creation of SecureRandom instance for session ID generation using
> [SHA1PRNG] took [9,870] milliseconds.
> 
> Maybe should you then start by fixing this, it has been discussed many
> times on the mailing list ( securerandom.source=file:/dev/./urandom )

Once Tomcat starts up, it should go fairly quickly. I don't know how
often SecureRandom re-seeds itself (or even if it does), but you only
need entropy during the seeding process. It shouldn't have any effect on
the throughput of a few thousand requests.

> Maybe are there some tests to do to understand if your Tomcat 6 seems fast
> because it uses some caching somewhere, or on the contrary if your Tomcat 8
> is slow because there is a bottleneck.
> I would try one scenario with one small HTML page requested thousands of
> times, and one very big file requested just 2 or 3 times, and compare
> results.
> 
> One thing which could help in understanding, have a look at the status
> servlet which gives statistics (
> http://tomcat.apache.org/tomcat-7.0-doc/apr.html )

Rafael, I'm curious: what is your testing procedure?

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Mark Thomas <ma...@apache.org>.
On 23/12/2015 20:29, Christopher Schultz wrote:

<snip/>

> Thanks for confirming that: often, we have people with two radically
> different setups wanting to know why things are behaving differently.
> 
> There have been many changes to the connector code between Tomcat 6 and
> Tomcat 8, mostly to make sure that as many code paths are shared between
> connectors (BIO, NIO, APR) as possible. I wouldn't have been surprised
> to see a measurable performance difference, but I figured it would be on
> the order of 10%-25%. Instead, you are seeing a 100%-150% difference.
> 
> Someone with more knowledge of the connector code

(me)

> would have to comment on what may be happening, here.

No idea. Use a profiler.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Christopher Schultz <ch...@christopherschultz.net>.
Aurélien,

On 12/24/15 4:17 AM, Aurélien Terrestris wrote:
> probably this won't solve your problem but I notice that the random seems
> slow :
> Creation of SecureRandom instance for session ID generation using
> [SHA1PRNG] took [9,870] milliseconds.
> 
> Maybe should you then start by fixing this, it has been discussed many
> times on the mailing list ( securerandom.source=file:/dev/./urandom )

Once Tomcat starts up, it should go fairly quickly. I don't know how
often SecureRandom re-seeds itself (or even if it does), but you only
need entropy during the seeding process. It shouldn't have any effect on
the throughput of a few thousand requests.

> Maybe are there some tests to do to understand if your Tomcat 6 seems fast
> because it uses some caching somewhere, or on the contrary if your Tomcat 8
> is slow because there is a bottleneck.
> I would try one scenario with one small HTML page requested thousands of
> times, and one very big file requested just 2 or 3 times, and compare
> results.
> 
> One thing which could help in understanding, have a look at the status
> servlet which gives statistics (
> http://tomcat.apache.org/tomcat-7.0-doc/apr.html )

Rafael, I'm curious: what is your testing procedure?

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Aurélien Terrestris <at...@gmail.com>.
Hi

probably this won't solve your problem but I notice that the random seems
slow :
Creation of SecureRandom instance for session ID generation using
[SHA1PRNG] took [9,870] milliseconds.

Maybe should you then start by fixing this, it has been discussed many
times on the mailing list ( securerandom.source=file:/dev/./urandom )

Maybe are there some tests to do to understand if your Tomcat 6 seems fast
because it uses some caching somewhere, or on the contrary if your Tomcat 8
is slow because there is a bottleneck.
I would try one scenario with one small HTML page requested thousands of
times, and one very big file requested just 2 or 3 times, and compare
results.

One thing which could help in understanding, have a look at the status
servlet which gives statistics (
http://tomcat.apache.org/tomcat-7.0-doc/apr.html )

best regards




2015-12-23 21:29 GMT+01:00 Christopher Schultz <chris@christopherschultz.net
>:

> Rafael,
>
> On 12/23/15 2:12 PM, Rafael Oliveira de Mattos wrote:
> > Christopher,
> >
> > Tomcat 6: boot.log
> > INFORMA합ES: Loaded APR based Apache Tomcat Native library 1.1.33 using
> APR version 1.5.2.
> > dez 14, 2015 5:32:14 PM org.apache.catalina.core.AprLifecycleListener
> init
> > INFORMA합ES: APR capabilities: IPv6 [true], sendfile [true], accept
> filters [false], random [true].
> > dez 14, 2015 5:32:15 PM org.apache.coyote.http11.Http11AprProtocol init
> > INFORMA합ES: Initializing Coyote HTTP/1.1 on http-8180
> > dez 14, 2015 5:32:15 PM org.apache.coyote.ajp.AjpAprProtocol init
> > INFORMA합ES: Initializing Coyote AJP/1.3 on ajp-8109
> > dez 14, 2015 5:32:15 PM org.apache.catalina.startup.Catalina load
> > INFORMA합ES: Initialization processed in 1155 ms
> > dez 14, 2015 5:32:15 PM org.apache.catalina.core.StandardService start
> > INFORMA합ES: Starting service Catalina
> > dez 14, 2015 5:32:15 PM org.apache.catalina.core.StandardEngine start
> > INFORMA합ES: Starting Servlet Engine: Apache Tomcat/6.0.36
> > dez 14, 2015 5:32:18 PM org.apache.catalina.core.ApplicationContext log
> > INFORMA합ES: Initializing Spring root WebApplicationContext
> > dez 14, 2015 5:32:25 PM org.apache.catalina.startup.HostConfig
> deployDescriptor
> > INFORMA합ES: Deploying configuration descriptor manager.xml
> > dez 14, 2015 5:32:26 PM org.apache.catalina.startup.HostConfig
> deployDescriptor
> > INFORMA합ES: Deploying configuration descriptor host-manager.xml
> > dez 14, 2015 5:32:26 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> > INFORMA합ES: Deploying web application directory ROOT
> > dez 14, 2015 5:32:27 PM org.apache.coyote.http11.Http11AprProtocol start
> > INFORMA합ES: Starting Coyote HTTP/1.1 on http-8180
> > dez 14, 2015 5:32:27 PM org.apache.coyote.ajp.AjpAprProtocol start
> > INFORMA합ES: Starting Coyote AJP/1.3 on ajp-8109
> > dez 14, 2015 5:32:27 PM org.apache.catalina.startup.Catalina start
> > INFORMA합ES: Server startup in 11791 ms
> >
> >
> > tomcat 8: boot_tomcat8.log
> > Dez 23, 2015 7:48:16 AM org.apache.catalina.core.AprLifecycleListener
> lifecycleEvent
> > INFORMAÇÕES: Loaded APR based Apache Tomcat Native library 1.1.33 using
> APR version 1.5.2.
> > Dez 23, 2015 7:48:16 AM org.apache.catalina.core.AprLifecycleListener
> lifecycleEvent
> > INFORMAÇÕES: APR capabilities: IPv6 [true], sendfile [true], accept
> filters [false], random [true].
> > Dez 23, 2015 7:48:16 AM org.apache.coyote.AbstractProtocol init
> > INFORMAÇÕES: Initializing ProtocolHandler ["http-apr-8180"]
> > Dez 23, 2015 7:48:16 AM org.apache.coyote.AbstractProtocol init
> > INFORMAÇÕES: Initializing ProtocolHandler ["ajp-apr-8109"]
> > Dez 23, 2015 7:48:16 AM org.apache.catalina.startup.Catalina load
> > INFORMAÇÕES: Initialization processed in 2341 ms
> > Dez 23, 2015 7:48:23 AM org.apache.jasper.servlet.TldScanner scanJars
> > INFORMAÇÕES: At least one JAR was scanned for TLDs yet contained no
> TLDs. Enable debug logging for this logger for a complete list of JARs that
> were scanned but no TLDs were found in them. Skipping unneeded JARs during
> scanning can improve startup time and JSP compilation time.
> > Dez 23, 2015 7:48:43 AM org.apache.catalina.util.SessionIdGeneratorBase
> createSecureRandom
> > INFORMAÇÕES: Creation of SecureRandom instance for session ID generation
> using [SHA1PRNG] took [9,870] milliseconds.
> >
> >
> > The apr loader configuration in both setup
> > <!--APR library loader. Documentation at /docs/apr.html -->
> > <Listener SSLEngine="off"
> className="org.apache.catalina.core.AprLifecycleListener"/>
>
> Thanks for confirming that: often, we have people with two radically
> different setups wanting to know why things are behaving differently.
>
> There have been many changes to the connector code between Tomcat 6 and
> Tomcat 8, mostly to make sure that as many code paths are shared between
> connectors (BIO, NIO, APR) as possible. I wouldn't have been surprised
> to see a measurable performance difference, but I figured it would be on
> the order of 10%-25%. Instead, you are seeing a 100%-150% difference.
>
> Someone with more knowledge of the connector code would have to comment
> on what may be happening, here.
>
> -chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: troughput difference

Posted by Christopher Schultz <ch...@christopherschultz.net>.
Rafael,

On 12/23/15 2:12 PM, Rafael Oliveira de Mattos wrote:
> Christopher,
> 
> Tomcat 6: boot.log
> INFORMA합ES: Loaded APR based Apache Tomcat Native library 1.1.33 using APR version 1.5.2.
> dez 14, 2015 5:32:14 PM org.apache.catalina.core.AprLifecycleListener init
> INFORMA합ES: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> dez 14, 2015 5:32:15 PM org.apache.coyote.http11.Http11AprProtocol init
> INFORMA합ES: Initializing Coyote HTTP/1.1 on http-8180
> dez 14, 2015 5:32:15 PM org.apache.coyote.ajp.AjpAprProtocol init
> INFORMA합ES: Initializing Coyote AJP/1.3 on ajp-8109
> dez 14, 2015 5:32:15 PM org.apache.catalina.startup.Catalina load
> INFORMA합ES: Initialization processed in 1155 ms
> dez 14, 2015 5:32:15 PM org.apache.catalina.core.StandardService start
> INFORMA합ES: Starting service Catalina
> dez 14, 2015 5:32:15 PM org.apache.catalina.core.StandardEngine start
> INFORMA합ES: Starting Servlet Engine: Apache Tomcat/6.0.36
> dez 14, 2015 5:32:18 PM org.apache.catalina.core.ApplicationContext log
> INFORMA합ES: Initializing Spring root WebApplicationContext
> dez 14, 2015 5:32:25 PM org.apache.catalina.startup.HostConfig deployDescriptor
> INFORMA합ES: Deploying configuration descriptor manager.xml
> dez 14, 2015 5:32:26 PM org.apache.catalina.startup.HostConfig deployDescriptor
> INFORMA합ES: Deploying configuration descriptor host-manager.xml
> dez 14, 2015 5:32:26 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFORMA합ES: Deploying web application directory ROOT
> dez 14, 2015 5:32:27 PM org.apache.coyote.http11.Http11AprProtocol start
> INFORMA합ES: Starting Coyote HTTP/1.1 on http-8180
> dez 14, 2015 5:32:27 PM org.apache.coyote.ajp.AjpAprProtocol start
> INFORMA합ES: Starting Coyote AJP/1.3 on ajp-8109
> dez 14, 2015 5:32:27 PM org.apache.catalina.startup.Catalina start
> INFORMA합ES: Server startup in 11791 ms
> 
> 
> tomcat 8: boot_tomcat8.log
> Dez 23, 2015 7:48:16 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
> INFORMAÇÕES: Loaded APR based Apache Tomcat Native library 1.1.33 using APR version 1.5.2.
> Dez 23, 2015 7:48:16 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
> INFORMAÇÕES: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> Dez 23, 2015 7:48:16 AM org.apache.coyote.AbstractProtocol init
> INFORMAÇÕES: Initializing ProtocolHandler ["http-apr-8180"]
> Dez 23, 2015 7:48:16 AM org.apache.coyote.AbstractProtocol init
> INFORMAÇÕES: Initializing ProtocolHandler ["ajp-apr-8109"]
> Dez 23, 2015 7:48:16 AM org.apache.catalina.startup.Catalina load
> INFORMAÇÕES: Initialization processed in 2341 ms
> Dez 23, 2015 7:48:23 AM org.apache.jasper.servlet.TldScanner scanJars
> INFORMAÇÕES: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
> Dez 23, 2015 7:48:43 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
> INFORMAÇÕES: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [9,870] milliseconds.
> 
> 
> The apr loader configuration in both setup
> <!--APR library loader. Documentation at /docs/apr.html -->
> <Listener SSLEngine="off" className="org.apache.catalina.core.AprLifecycleListener"/>

Thanks for confirming that: often, we have people with two radically
different setups wanting to know why things are behaving differently.

There have been many changes to the connector code between Tomcat 6 and
Tomcat 8, mostly to make sure that as many code paths are shared between
connectors (BIO, NIO, APR) as possible. I wouldn't have been surprised
to see a measurable performance difference, but I figured it would be on
the order of 10%-25%. Instead, you are seeing a 100%-150% difference.

Someone with more knowledge of the connector code would have to comment
on what may be happening, here.

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Rafael Oliveira de Mattos <ra...@softplan.com.br>.
Christopher,

Tomcat 6: boot.log
INFORMA합ES: Loaded APR based Apache Tomcat Native library 1.1.33 using APR version 1.5.2.
dez 14, 2015 5:32:14 PM org.apache.catalina.core.AprLifecycleListener init
INFORMA합ES: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
dez 14, 2015 5:32:15 PM org.apache.coyote.http11.Http11AprProtocol init
INFORMA합ES: Initializing Coyote HTTP/1.1 on http-8180
dez 14, 2015 5:32:15 PM org.apache.coyote.ajp.AjpAprProtocol init
INFORMA합ES: Initializing Coyote AJP/1.3 on ajp-8109
dez 14, 2015 5:32:15 PM org.apache.catalina.startup.Catalina load
INFORMA합ES: Initialization processed in 1155 ms
dez 14, 2015 5:32:15 PM org.apache.catalina.core.StandardService start
INFORMA합ES: Starting service Catalina
dez 14, 2015 5:32:15 PM org.apache.catalina.core.StandardEngine start
INFORMA합ES: Starting Servlet Engine: Apache Tomcat/6.0.36
dez 14, 2015 5:32:18 PM org.apache.catalina.core.ApplicationContext log
INFORMA합ES: Initializing Spring root WebApplicationContext
dez 14, 2015 5:32:25 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFORMA합ES: Deploying configuration descriptor manager.xml
dez 14, 2015 5:32:26 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFORMA합ES: Deploying configuration descriptor host-manager.xml
dez 14, 2015 5:32:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFORMA합ES: Deploying web application directory ROOT
dez 14, 2015 5:32:27 PM org.apache.coyote.http11.Http11AprProtocol start
INFORMA합ES: Starting Coyote HTTP/1.1 on http-8180
dez 14, 2015 5:32:27 PM org.apache.coyote.ajp.AjpAprProtocol start
INFORMA합ES: Starting Coyote AJP/1.3 on ajp-8109
dez 14, 2015 5:32:27 PM org.apache.catalina.startup.Catalina start
INFORMA합ES: Server startup in 11791 ms


tomcat 8: boot_tomcat8.log
Dez 23, 2015 7:48:16 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFORMAÇÕES: Loaded APR based Apache Tomcat Native library 1.1.33 using APR version 1.5.2.
Dez 23, 2015 7:48:16 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFORMAÇÕES: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Dez 23, 2015 7:48:16 AM org.apache.coyote.AbstractProtocol init
INFORMAÇÕES: Initializing ProtocolHandler ["http-apr-8180"]
Dez 23, 2015 7:48:16 AM org.apache.coyote.AbstractProtocol init
INFORMAÇÕES: Initializing ProtocolHandler ["ajp-apr-8109"]
Dez 23, 2015 7:48:16 AM org.apache.catalina.startup.Catalina load
INFORMAÇÕES: Initialization processed in 2341 ms
Dez 23, 2015 7:48:23 AM org.apache.jasper.servlet.TldScanner scanJars
INFORMAÇÕES: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Dez 23, 2015 7:48:43 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
INFORMAÇÕES: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [9,870] milliseconds.


The apr loader configuration in both setup
<!--APR library loader. Documentation at /docs/apr.html -->
<Listener SSLEngine="off" className="org.apache.catalina.core.AprLifecycleListener"/>


----- Mensagem original -----
De: "Christopher Schultz" <ch...@christopherschultz.net>
Para: "Tomcat Users List" <us...@tomcat.apache.org>
Enviadas: Quarta-feira, 23 de dezembro de 2015 16:17:17
Assunto: Re: troughput difference

Rafael,

On 12/23/15 9:17 AM, Rafael Oliveira de Mattos wrote:
> We are using the APR connector in both cases.

Can you confirm you are using the same version of tcnative/APR/OpenSSL
in both cases?

Can you please copy/paste the startup messages from each version?

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Christopher Schultz <ch...@christopherschultz.net>.
Rafael,

On 12/23/15 9:17 AM, Rafael Oliveira de Mattos wrote:
> We are using the APR connector in both cases.

Can you confirm you are using the same version of tcnative/APR/OpenSSL
in both cases?

Can you please copy/paste the startup messages from each version?

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Rafael Oliveira de Mattos <ra...@softplan.com.br>.
We are using the APR connector in both cases.

Att.

Rafael Oliveira de Mattos
Analista Implementador
Unidade de Justiça
Softplan/Poligraph
+55 48 3027-8000
www.softplan.com.br
twitter.com/softplanonline

----- Mensagem original -----
De: "Christopher Schultz" <ch...@christopherschultz.net>
Para: "Tomcat Users List" <us...@tomcat.apache.org>
Enviadas: Terça-feira, 22 de dezembro de 2015 21:09:07
Assunto: Re: troughput difference

Rafael.

On 12/21/15 1:48 PM, Rafael Oliveira de Mattos wrote:
> We are using only the http connector. Here is the configuration:
> 
> <Connector port="${port.http}" protocol="HTTP/1.1"
> redirectPort="${port.https}" connectionTimeout="60000"
> useBodyEncodingForURI="true" maxThreads="1400"
> acceptorThreadCount="4" acceptCount="300" minSpareThreads="80"/>

In Tomcat 6, you are using the BIO connector, or possibly the APR
connector. Do you know which you are using?

In Tomcat 8, you are using the NIO connector, or possibly the APR
connector. Do you know which you are using?

When Tomcat starts, it will tell you what kind of connector it is using
like this:

Dec 22, 2015 10:16:52 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8015"]
Dec 22, 2015 10:16:52 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-8017"]
Dec 22, 2015 10:16:52 AM org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector

Here you can see I have an AJP BIO-based connector on port 8015 and an
HTTP NIO-based connector on port 8017.

Let's make sure we are comparing apples to apples, here.

-chris

> ----- Mensagem original ----- De: "Christopher Schultz"
> <ch...@christopherschultz.net> Para: "Tomcat Users List"
> <us...@tomcat.apache.org> Enviadas: Segunda-feira, 21 de dezembro de
> 2015 14:33:31 Assunto: Re: troughput difference
> 
> Rafael,
> 
> On 12/17/15 3:09 PM, Rafael Oliveira de Mattos wrote:
>> I'm having different results in Tomcat performance using version
>> 6.0.37 and 8.0.23.
>> 
>> Using tomcat 6 we usually have 5000 ~ rpm with a response time of
>> 80ms
>> 
>> Using tomcat 8 the max that we can get is 2000 ~ rpm with a
>> response time of 200ms
>> 
>> We are using the same jdk version 1.7.0.80, a nd the same
>> applications on both version, they are installed in the same
>> machine and using APR, but not running at the same time. We tried
>> to use the same configuration whenever possible.
>> 
>> SO: Linux ubuntu 12.04 JDK: 1.7.0.80 Anything I should take look at
>> it?
> 
> How are your <Connector>s defined in server.xml in each setup?
> 
> -chris
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Christopher Schultz <ch...@christopherschultz.net>.
Rafael.

On 12/21/15 1:48 PM, Rafael Oliveira de Mattos wrote:
> We are using only the http connector. Here is the configuration:
> 
> <Connector port="${port.http}" protocol="HTTP/1.1"
> redirectPort="${port.https}" connectionTimeout="60000"
> useBodyEncodingForURI="true" maxThreads="1400"
> acceptorThreadCount="4" acceptCount="300" minSpareThreads="80"/>

In Tomcat 6, you are using the BIO connector, or possibly the APR
connector. Do you know which you are using?

In Tomcat 8, you are using the NIO connector, or possibly the APR
connector. Do you know which you are using?

When Tomcat starts, it will tell you what kind of connector it is using
like this:

Dec 22, 2015 10:16:52 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8015"]
Dec 22, 2015 10:16:52 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-8017"]
Dec 22, 2015 10:16:52 AM org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector

Here you can see I have an AJP BIO-based connector on port 8015 and an
HTTP NIO-based connector on port 8017.

Let's make sure we are comparing apples to apples, here.

-chris

> ----- Mensagem original ----- De: "Christopher Schultz"
> <ch...@christopherschultz.net> Para: "Tomcat Users List"
> <us...@tomcat.apache.org> Enviadas: Segunda-feira, 21 de dezembro de
> 2015 14:33:31 Assunto: Re: troughput difference
> 
> Rafael,
> 
> On 12/17/15 3:09 PM, Rafael Oliveira de Mattos wrote:
>> I'm having different results in Tomcat performance using version
>> 6.0.37 and 8.0.23.
>> 
>> Using tomcat 6 we usually have 5000 ~ rpm with a response time of
>> 80ms
>> 
>> Using tomcat 8 the max that we can get is 2000 ~ rpm with a
>> response time of 200ms
>> 
>> We are using the same jdk version 1.7.0.80, a nd the same
>> applications on both version, they are installed in the same
>> machine and using APR, but not running at the same time. We tried
>> to use the same configuration whenever possible.
>> 
>> SO: Linux ubuntu 12.04 JDK: 1.7.0.80 Anything I should take look at
>> it?
> 
> How are your <Connector>s defined in server.xml in each setup?
> 
> -chris
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Rafael Oliveira de Mattos <ra...@softplan.com.br>.
Christopher,


We are using only the http connector. Here is the configuration:

<Connector port="${port.http}" protocol="HTTP/1.1" redirectPort="${port.https}" connectionTimeout="60000" useBodyEncodingForURI="true" maxThreads="1400" acceptorThreadCount="4" acceptCount="300" minSpareThreads="80"/>

The server has 8 cores.


-Rafael

----- Mensagem original -----
De: "Christopher Schultz" <ch...@christopherschultz.net>
Para: "Tomcat Users List" <us...@tomcat.apache.org>
Enviadas: Segunda-feira, 21 de dezembro de 2015 14:33:31
Assunto: Re: troughput difference

Rafael,

On 12/17/15 3:09 PM, Rafael Oliveira de Mattos wrote:
> I'm having different results in Tomcat performance using version 6.0.37 and 8.0.23. 
> 
> Using tomcat 6 we usually have 
> 5000 ~ rpm with a response time of 80ms 
> 
> Using tomcat 8 the max that we can get is 
> 2000 ~ rpm with a response time of 200ms 
> 
> We are using the same jdk version 1.7.0.80, a nd the same applications on both version, they are installed in the same machine and using APR, but not running at the same time. 
> We tried to use the same configuration whenever possible. 
> 
> SO: Linux ubuntu 12.04 
> JDK: 1.7.0.80 
> Anything I should take look at it? 

How are your <Connector>s defined in server.xml in each setup?

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: troughput difference

Posted by Christopher Schultz <ch...@christopherschultz.net>.
Rafael,

On 12/17/15 3:09 PM, Rafael Oliveira de Mattos wrote:
> I'm having different results in Tomcat performance using version 6.0.37 and 8.0.23. 
> 
> Using tomcat 6 we usually have 
> 5000 ~ rpm with a response time of 80ms 
> 
> Using tomcat 8 the max that we can get is 
> 2000 ~ rpm with a response time of 200ms 
> 
> We are using the same jdk version 1.7.0.80, a nd the same applications on both version, they are installed in the same machine and using APR, but not running at the same time. 
> We tried to use the same configuration whenever possible. 
> 
> SO: Linux ubuntu 12.04 
> JDK: 1.7.0.80 
> Anything I should take look at it? 

How are your <Connector>s defined in server.xml in each setup?

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org