<div dir="ltr"><div>Yes it will, there is also:</div><div><br></div><dt><strong><span class="gmail-code">session_cache_client_max = integer() <optional></span><br></strong></dt>
<dd><p>Limits the growth of the clients session cache, that is
how many sessions towards servers that are cached to be used by
new client connections. If the maximum number of sessions is
reached, the current cache entries will be invalidated
regardless of their remaining lifetime. Defaults to
1000. Recommended ssl-8.2.1 or later for this option to work as intended.</p></dd>
<dt><strong> <span class="gmail-code">session_cache_server_max = integer() <optional></span></strong></dt>
<dd><p>Limits the growth of the servers session cache, that is
how many client sessions are cached by the server. If the
maximum number of sessions is reached, the current cache entries
will be invalidated regardless of their remaining
lifetime. Defaults to 1000. Recommended ssl-8.2.1 or later for this option to work as intended.</p></dd><dt><br></dt><dt>Regards Ingela<br></dt></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Den fre 23 aug. 2019 kl 15:31 skrev Oliver Bollmann <<a href="mailto:oliver.bollmann@t-online.de">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">
<div bgcolor="#FFFFFF">
<pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo"">-ssl session_lifetime 120; each 2 minutes
will delete sessions from server_ssl_opt_session_cache
Right?
Oliver</pre>
<div class="gmail-m_3945276711196827101moz-cite-prefix">On 23.08.19 14:52, Ingela Andin wrote:<br>
</div>
<blockquote type="cite">
<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" target="_blank">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">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote>
</div>
</div>
</blockquote>
<pre class="gmail-m_3945276711196827101moz-signature" cols="72">--
Grüße
Oliver Bollmann</pre>
</div>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>