Hello Valters, On Wed, Jan 6, 2021 at 4:26 PM Valters Jansons <[email protected]> wrote: > 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?
(ccing who did the last modification on this doc) I believe this is based on `sizeof(struct sh_ssl_sess_hdr) + SHSESS_BLOCK_MIN_SIZE` calculation used for `shctx_init` function, which is still 200 bytes today. > Could the documentation be updated to include such > information? I will send a proposal patch. > From a configuration perspective - could it be possible to only > provide the preferred footprint (memory size) instead of providing the > number of blocks? I will let Erneric or William L. answer this one. -- William
