Hello,

There is already a property to set the cache size, would it be enough to 
re-purpose a cache size of 0 to turn it off?

Are there numbers to show when this is actually a problem? Is this only for 
100% Cache misses? Maybe the cache itself needs some optimizations? (It is hard 
to imagine that a saved handshake does not compensate for hundreds of gets - 
especially if the current version still would generate a cache key)

Gruss
Bernd

Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
From: security-dev <security-dev-boun...@openjdk.java.net> on behalf of Ivan 
Gerasimov <ivan.gerasi...@oracle.com>
Sent: Wednesday, November 8, 2017 3:24:54 AM
To: security-dev@openjdk.java.net
Subject: [10] RFR : 8186628 : SSL session cache can cause a scalability 
bottleneck

Hello everybody!

The class sun.security.ssl.SSLSessionContextImpl maintains caches for
the sessions reuse.
Access to the cache from threads is serialized.
It was reported that under heavy load the time of waiting for the turn
to access the synchronized methods outweighs the time of creating a new
session.

It is proposed to introduce a flag that will allow to avoid using the
cache altogether.
Would you please help review the proposed fix?

BUGURL: https://bugs.openjdk.java.net/browse/JDK-8186628
WEBREV: http://cr.openjdk.java.net/~igerasim/8186628/00/webrev/

--
With kind regards,
Ivan Gerasimov

Reply via email to