Re: [AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Dossy Shiobara
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 alwa

Re: [AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Dossy Shiobara
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

Re: [AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Tom Jackson
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

Re: [AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Tom Jackson
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

Re: [AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Shedi Shedi
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 qu

Re: [AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Dossy Shiobara
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 maxthread

[AOLSERVER] understanding ns_pools behaviour on 4.5

2007-09-14 Thread Shedi Shedi
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 start