-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
None
SSL startHandshake profiles show that a significant time is spent on HandshakeContext initialization to get the
activeCipherSuite and activeProtocols, These parameters depends on configuration already available to the client/
server and does not depend on the response from the server/client.
We propose moving these to the SSLSocketFactory and reusing the activeCipherSuite and activeProtocols instead of
creating these for each handshake.This could improve the efficiency of the handshake process by reducing the computation
needed for creating these lists.
Please find attached the JFR profiles for handshake process. I've also attached benchmarks from the proof of concept for
the above proposed method.
activeCipherSuite and activeProtocols, These parameters depends on configuration already available to the client/
server and does not depend on the response from the server/client.
We propose moving these to the SSLSocketFactory and reusing the activeCipherSuite and activeProtocols instead of
creating these for each handshake.This could improve the efficiency of the handshake process by reducing the computation
needed for creating these lists.
Please find attached the JFR profiles for handshake process. I've also attached benchmarks from the proof of concept for
the above proposed method.
- relates to
-
JDK-8285398 Cache the results of constraint checks
- Resolved
- links to
-
Review openjdk/jdk/5793