<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<pre style="background-color:#ffffff;color:#000000;font-family:'Menlo';font-size:18,0pt;">-ssl session_lifetime 120; each 2 minutes
will delete sessions from server_ssl_opt_session_cache
Right?
Oliver</pre>
<div class="moz-cite-prefix">On 23.08.19 14:52, Ingela Andin wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFj9NSSg9Rx7_xyD=pV4gf_D4=9QzWQWEG44vZfainhs3nvhEw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi!</div>
<div><br>
</div>
<div> {reuse_sessions,false} just makes the current connection
not use the feature but the information is</div>
<div>saved for possible other connections to use it, as it is
configured per connection and the ssl application can not know</div>
<div>if might need it later.<br>
</div>
<div><br>
</div>
<div>Since ssl-8.2.1 there should be a working limitation of the
table, although it is a soft limit due to current
implementation trade offs, and it will be shrieked gradually.
At a very high load it might shrink to slow, the workaround
would be to have a callback for the session table that does
not save the information. <br>
</div>
<div><br>
</div>
<div> We been thinking about changing the implementation but
TLS-1.3 has a new mechanism, and there is also other
mechanisms for TLS 1.2 the we have not implemented so it just
have not landed in best way forward yet. <br>
</div>
<div><br>
</div>
<div>Regards Ingela - Erlang/OTP Team - Ericsson AB<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> <br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Den fre 23 aug. 2019 kl
14:18 skrev Oliver Bollmann <<a
href="mailto:oliver.bollmann@t-online.de"
moz-do-not-send="true">oliver.bollmann@t-online.de</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
we have 5000 clients(third party) connecting each 25 seconds
to our <br>
server over tls 1.2,<br>
<br>
24h later the table server_ssl_opt_session_cache has about
18 million <br>
objects and allocate 5GByte!<br>
<br>
If we use {reuse_sessions,false} the
table(server_ssl_opt_session_cache) <br>
is not empty!<br>
<br>
Any hints?<br>
<br>
-- <br>
Grüße<br>
Oliver Bollmann<br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank"
moz-do-not-send="true">erlang-questions@erlang.org</a><br>
<a
href="http://erlang.org/mailman/listinfo/erlang-questions"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Grüße
Oliver Bollmann</pre>
</body>
</html>