Re: TLS handshake performance

2017-06-06 Thread Jeff Elsloo
Hi Mark, Apologies for the late reply on this, but I was the person that asked you this performance question at ApacheCon. We reviewed this thread and appreciate the analysis and discussion. The description below is accurate; we have short lived non-keep-alived clients, so we're keenly interested

Re: TLS handshake performance

2017-05-19 Thread Rémy Maucherat
2017-05-19 16:28 GMT+02:00 Christopher Schultz : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Rémy, > > On 5/19/17 8:47 AM, Rémy Maucherat wrote: > > 2017-05-19 14:42 GMT+02:00 Christopher Schultz > > >> : > > > >> But here it's clear that the client wants to know "do I get a > >> perf

Re: TLS handshake performance

2017-05-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rémy, On 5/19/17 8:47 AM, Rémy Maucherat wrote: > 2017-05-19 14:42 GMT+02:00 Christopher Schultz > > : > >> But here it's clear that the client wants to know "do I get a >> performance benefit swapping-out JSSE for OpenSSL. I think we all >> knew

Re: TLS handshake performance

2017-05-19 Thread Rémy Maucherat
2017-05-19 14:42 GMT+02:00 Christopher Schultz : > But here it's clear that the client wants to know "do I get a > performance benefit swapping-out JSSE for OpenSSL. I think we all knew > what the answer was. Jean-Frederick's slides from yesterday I believe > include such benchmarks as well (NIO/O

Re: TLS handshake performance

2017-05-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 5/18/17 9:47 AM, Mark Thomas wrote: > On 18/05/2017 06:04, Christopher Schultz wrote: Mark, > > On 5/17/17 5:31 PM, Mark Thomas wrote: I got asked in the corridor at TomcatCon earlier today what the relative performance of the TL

Re: TLS handshake performance

2017-05-18 Thread Rainer Jung
Am 18.05.2017 um 16:03 schrieb john.e.gr...@wellsfargo.com.INVALID: -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Thursday, May 18, 2017 8:47 AM To: users@tomcat.apache.org Subject: Re: TLS handshake performance This time to the right list... On 18/05/2017 06:04

RE: TLS handshake performance

2017-05-18 Thread John.E.Gregg
> -Original Message- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Thursday, May 18, 2017 8:47 AM > To: users@tomcat.apache.org > Subject: Re: TLS handshake performance > > This time to the right list... > > On 18/05/2017 06:04, Christopher Schult

Re: TLS handshake performance

2017-05-18 Thread Mark Thomas
This time to the right list... On 18/05/2017 06:04, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 5/17/17 5:31 PM, Mark Thomas wrote: I got asked in the corridor at TomcatCon earlier today what the relative performance of the TLS handshake was with 8.5.x,

Re: TLS handshake performance

2017-05-18 Thread Rémy Maucherat
2017-05-17 23:31 GMT+02:00 Mark Thomas : > Hi all, > > I got asked in the corridor at TomcatCon earlier today what the relative > performance of the TLS handshake was with 8.5.x, the NIO connector and JSSE > vs OpenSSL TLS implementation. > > This might be something that is of interest to a wider

Re: TLS handshake performance

2017-05-18 Thread Rémy Maucherat
2017-05-18 7:04 GMT+02:00 Christopher Schultz : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On 5/17/17 5:31 PM, Mark Thomas wrote: > > I got asked in the corridor at TomcatCon earlier today what the > > relative performance of the TLS handshake was with 8.5.x, the NIO > > co

Re: TLS handshake performance

2017-05-17 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 5/17/17 5:31 PM, Mark Thomas wrote: > I got asked in the corridor at TomcatCon earlier today what the > relative performance of the TLS handshake was with 8.5.x, the NIO > connector and JSSE vs OpenSSL TLS implementation. I'm curious abou

TLS handshake performance

2017-05-17 Thread Mark Thomas
Hi all, I got asked in the corridor at TomcatCon earlier today what the relative performance of the TLS handshake was with 8.5.x, the NIO connector and JSSE vs OpenSSL TLS implementation. This might be something that is of interest to a wider audience so here goes... The following results