On 06.11.19 17:52, David Osborne wrote:
The RSS size of our nsd process is often ~2GB but does occasionally
stray as far as 4GB.
the RSS chart looks quite ok in terms of growth. What you can see it
that when using zippy malloc,
the memory never shrinks. So, one i more likely running into memory
Hi Gustaf,
Thanks for the very detailed response!
I had an inkling that nsproxy might be the answer - we'll look at making
this change.
The RSS size of our nsd process is often ~2GB but does occasionally stray
as far as 4GB. (The small spike on the right of the attached graph is when
this particul
Dear David,
Technically, every unix fork() creates a new process by duplicating the
calling process.
If the calling process is large this can lead to the problem you are
mentioning.
However, on Linux uses a copy-on-write. This means that while after the
fork,
both processes might show RSS of 4
Hi,
I was wondering if anyone could point us in the right direction with an
intermittent problem we're seeing. Apologies for the wooly problem
description - we don't have a firm test case as of yet.
These instances are running NaviServer/4.99.16d10 on Debian Jessie 8.10
The problem usually manif
