Hi,
I'm running stunnel 5.63 compiled in debian-bullseye inside docker, and i'm trying to understand the allocated memory behavior In a test i'm conducting i'm creating a load towards the stunnel server And the process CPU + memory consumption rises. Once i stop the traffic the CPU goes down but the memory doesn't. Is this expected ?
Many Thanks, Roie
Hi Roie,
Yes it is. Not all of the allocated heap memory can be reclaimed due to fragmentation. See https://www.design-reuse.com/articles/25090/dynamic-memory-allocation-fragme... for more details.
Best regards, Mike
On 6/25/22 20:59, roie rachamim wrote:
Hi,
I'm running stunnel 5.63 compiled in debian-bullseye inside docker, and i'm trying to understand the allocated memory behavior In a test i'm conducting i'm creating a load towards the stunnel server And the process CPU + memory consumption rises. Once i stop the traffic the CPU goes down but the memory doesn't. Is this expected ?
Many Thanks, Roie
stunnel-users mailing list -- stunnel-users@stunnel.org To unsubscribe send an email to stunnel-users-leave@stunnel.org
-
Michał Trojnara -
roie rachamim