Re: https server - memory leaks

In this case, since curl doesn't keep any state between requests, each request would count as a new client. (Whenever a client connects and doesn't pass an existing session ID as part of the TLS handshake, the server will allocate a new session for it.) And since states are currently only cleaned up when they're at least an hour old, your test would never hit the cleanup code, so yes, it would grow linearly.

That behaviour is not really smart, especially in a memory limited context with spikes in the number of requests per second it is doomed to fail or get killed by the kernel's OOM killer.

I will have a look into it to write some patches making the TTL for cache entries configureable (unless somebody/you are doing that already).



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]