Thanks for the pat on my back.
Yesterday evening i restarted the nsd, and this morning in the server
logs there are no indications of idle threads exiting. Either under
normal log level its not written to log as opposed to threads that
reached max connection limits.
ns_pools shows that:
Hi Dossy,
You said that current should never drop below min. But in my case after
threads have serviced configured number of requests they start to die. idle
and current keeps dropping until 0 and never comes up again.
The server logs shows lines like:
You're not doing anything wrong. You have a thread timeout. So after 60
seconds, the idle thread exits. Maybe there is a bug in pools.c, but what is
happening is that at startup, minthreads are created. If you go in and
increase minthreads after starup of the pool, the minthreads will not
Thanks for the explanations but i'm still confused by the numbers shown by
my ns_pools:
ns pool config:
ns_pools set procmsgmgr -maxconns 150 -maxthreads 500 -minthreads 300
-timeout 60
At peak times when i look at the pools it shows that idle=1 and current=1
nspools=minthreads 300 maxthreads
I have a pool defined in config.tcl as:
ns_pools set procmsgmgr -maxconns 5 -maxthreads 200 -minthreads 50 -timeout
120
when i start the server ns_pools get procmsgmgr command returns:
nspools=minthreads 50 maxthreads 200 idle 50 current 50 maxconns 5 queued 0
timeout 120
after the server
On 2007.09.14, Shedi Shedi [EMAIL PROTECTED] wrote:
...
After serving about 255 request the ns_pools get returns the following:
nspools=minthreads 50 maxthreads 200 idle 25 current 25 maxconns 5 queued
225 timeout 120
...
Why did you set maxconns so low? Setting minthreads or maxthreads
I check the docs and previous posts regarding maxconns, that it is the
number of connections that will be served by a single thread before it
dies.
also the queued value always increases, when a new request arrives the queue
value is incremented. But it never goes downwards.
Does this mean the
On Friday 14 September 2007 06:58, Shedi Shedi wrote:
I check the docs and previous posts regarding maxconns, that it is the
number of connections that will be served by a single thread before it
dies.
Yeah, I think this is right. maxthreads indicates how many you can service at
once. I
On Friday 14 September 2007 05:02, Dossy Shiobara wrote:
queued show show many pending connections are waiting in queue to be
handed off to a worker thread.
I noticed this number just goes up also. I think, at least as it works right
now that queued means how many total connections have come
On 2007.09.14, Tom Jackson [EMAIL PROTECTED] wrote:
On Friday 14 September 2007 06:58, Shedi Shedi wrote:
I check the docs and previous posts regarding maxconns, that it is the
number of connections that will be served by a single thread before it
dies.
Yeah, I think this is right.
On 2007.09.14, Shedi Shedi [EMAIL PROTECTED] wrote:
I check the docs and previous posts regarding maxconns, that it is the
number of connections that will be served by a single thread before
it dies.
Yes, I was incorrect about this. Thanks for the correction.
also the queued value always
11 matches
Mail list logo
