Hi Maciej, On Mon, Nov 27, 2017 at 09:15:22AM +0100, Maciej Zdeb wrote: > Hi, > > Thank you for your hard work on HAProxy 1.8 - great job! > > I tried to update haproxy from 1.7 on our r&d machine to 1.8 version > however stumbled upon problem with tune.ssl.cachesize directive. > > In 1.7.3 with tune.ssl.cachesize = 10000000: > > ps aux | grep haproxy > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > haproxy 43863 0.1 0.0 2327496 13052 ? Ss 08:54 0:00 > /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D > > Note VSZ is 2327496. > > In 1.8.0 with tune.ssl.cachesize = 10000000: > [ALERT] 330/085923 (30585) : Unable to allocate SSL session cache. > > In 1.8.0 with tune.ssl.cachesize = 3000000: > ps aux | grep haprox > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > haproxy 34539 0.0 0.4 30342220 163784 ? Ss 09:01 0:00 > /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid > > Note VSZ is 30342220. > > In docs i don't see any related change: > http://cbonte.github.io/haproxy-dconv/1.8/configuration.html#3.2-tune. > ssl.cachesize > http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#3.2-tune. > ssl.cachesize > > What is the proper way to calculate ssl cachesize in 1.8? Is it bug or docs > need update?
Wow, multiplied by 15! It looks like each entry now takes 3kB instead of 200 bytes, maybe something has changed with the default block size. CCing William for advice. Thanks, Willy