: Friday, May 15, 2015 3:12 PM
Subject: Re: Http 2 support in Tomcat
Am 15.05.2015 um 20:43 schrieb PerfGuru:
> Thanks Mark & Chris this is a very informative. I am using a httpd that
> supports http/2 and wow is it impressive. Sorry, I had to stop using
> Apache/Tomcat to u
Schultz
To: Tomcat Users List
Sent: Friday, May 15, 2015 2:49 PM
Subject: Re: Http 2 support in Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony,
On 5/15/15 2:43 PM, PerfGuru wrote:
> Thanks Mark & Chris this is a very informative. I am using a httpd
> that suppo
sers List
Sent: Friday, May 15, 2015 12:28 PM
Subject: Re: Http 2 support in Tomcat
On 15/05/2015 19:23, Christopher Schultz wrote:
> Mark,
>
> On 5/15/15 12:59 PM, Mark Thomas wrote:
>> On 15/05/2015 17:49, Christopher Schultz wrote:
>>> Tony,
>>>
>>>
Good news thanks for the update. It may be some time before servlet 4 support
is released but good to know Tomcat will be ready then.But does APR support
http/2? I know other web servers now do. Also, I think Tomcat supports
websockets which has the important capabilities that http/2 has and has
Here is the bug reference I found:https://jira.spring.io/i#browse/SPR-11335
Regards,-Tony
From: "Balana, Vishal"
To: Tomcat Users List ; PerfGuru
; Jeffrey Janner
Sent: Tuesday, April 14, 2015 8:19 AM
Subject: RE: Performance question...
Could you please share the refe
cache but as
expected it did not make a difference. Again thanks for all the
suggestions.-Tony
From: Jeffrey Janner
To: 'Tomcat Users List' ; 'PerfGuru'
Sent: Friday, April 10, 2015 1:03 PM
Subject: RE: Performance question...
> -Original Messag
utilization
issues. The fix is to try increasing to 4x the default size, setup printing out
codecashe size when app server stopped. Also in 1.7.0_80 this was fixed and in
1.8 the default codecache size was increased by 4x. Regards,-Tony
From: Linus Brimstedt
To: PerfGuru ; users
Hi All,We are noticing when running a simple load test of 25 virtual users that
our Tomcat server is running at 40% CPU and transactions are taking over 40
seconds. We setup a test where we focused (in a loop) one of the longer
response time requests. The access logs show the log response time a
