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
problems, when
the machine has limited resources. So, probably some weekly restarts
might help as well
to come back from 4GB to 2GB....
One thing, you have to watch out concerning memory size is to avoid
reading files
into Tcl_Objs (sooner or later, one encounters large file) or - even
worse -
appending to large strings. Tcl has a memory-doubling strategy (it
over-allocates
memory such it can do append operations quickly). So, when you add a
single byte
to a Tcl_Obj with e.g. 500MB, you might end up with 1GB memory
allocation for a
single Tcl_Obj.
Using nsproxy: you might look at the "exec" definition of OpenACS. It
redefines
Tcl's "exec" via a proxy::exec using nsproxy [1].
> is the patch referred to online somewhere?
look into [2].
all the best
-g
[1]
https://github.com/openacs/openacs-core/blob/oacs-5-10/packages/acs-tcl/tcl/proxy-procs.tcl
[2] https://github.com/gustafn/install-ns/blob/master/install-ns.sh#L501
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
