Hello everyone, There is a global parameter for SSL session cache block count (tune.ssl.cachesize). Documentation for it currently states: A block uses approximately 200 bytes of memory.
This estimate of 200B for each block has been there since version 1.5, and it does not seem to align with what we are seeing on our systems where it is a bit below 300B at first glance. Could some more details be provided on how the 200 bytes number was established? Could the documentation be updated to include such information? >From a configuration perspective - could it be possible to only provide the preferred footprint (memory size) instead of providing the number of blocks?
