On 23/02/16 17:30, Amos Jeffries wrote: > And a leak (real or pseudo) means they are still hanging around in > memory for some reason other than cert-cache references (being in the > cache by definition is not-leaking). For example as part of active TLS > sessions when the core was produced. Seems pretty unlikely that there were over 130 thousand active TLS sessions in just one of 2 worker threads at the time the core was generated. I'm seeing Squid processes continually increase to many gigabytes in size before I have to restart them to avoid the servers ending up deep in swap. If this was just things held during "active sessions" I would expect to see the memory freed up again over night when there isn't much traffic - I see no such reduction in memory usage. -- - Steve Hill Technical Director Opendium Limited http://www.opendium.com Direct contacts: Instant messager: xmpp:steve@xxxxxxxxxxxx Email: steve@xxxxxxxxxxxx Phone: sip:steve@xxxxxxxxxxxx Sales / enquiries contacts: Email: sales@xxxxxxxxxxxx Phone: +44-1792-825748 / sip:sales@xxxxxxxxxxxx Support contacts: Email: support@xxxxxxxxxxxx Phone: +44-1792-824568 / sip:support@xxxxxxxxxxxx _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
