Jeff Rogers wrote:
> I'm confusing myself now tho, because it certainly looks like the
> threads are only ever reaped by the driver thread, which should
> absolutely finish Ns_ThreadCreate before it can call it again. Conn
> threads create a new thread to replace themselves when they hit
> maxcon
Jim Davidson wrote:
>
> Howdy,
>
> The leak is more precisely bloat, i.e., Tcl interps that create more
> and more objects and [...] The memory is not
> actually "returned" via a munmap, e.g.. Nate Folkman and I spent
> tons of time trying to figure this out years ago with all sorts of
> coalesc
Hi,
I really appreciate your help with this. I got things working now.
The interaction between these various variables re pools.tcl is interesting and
not intuitive for me. I ended up leaving the code in pools.tcl alone and set
the configuration file to:
ns_section "ns/server/${servername}"
Howdy,
The leak is more precisely bloat, i.e., Tcl interps that create more and more
objects and various per-thread thingers that grow in size and hang around,
e.g., ADP caches and output buffers. These resources are somewhat reclaimed
when a thread exists. But, assuming the normal "zippy"
Bjoern Kiesbye wrote:
> Hi Thorpe, I think Aolserver 4.5.0 ignores this settings from
> config.tcl, and if not set explicitly using ns_pools set command,
> Aolserver will use deafult values. I would suggest to in crease the
> maxconns value to at least 100, it does not cost extra pre occupied
> re
