On 2007.08.11, Tom Jackson <[EMAIL PROTECTED]> wrote:
> 1. The new default and error pools remain initialized as follows (same as 
> before):
> minthreads 0 
> maxthreads 10
> maxconns 0 
> timeout 120
> Although I'm not  sure why this is considered 'unlimited'.

"maxconns" set to 0 means "unlimited."

> 2. ns_pools is used to configure server specific pools, the API has not 
> changed. However, the server name is prepended to the pool name supplied:
> 'ns_pools set fast' in server named 'jnm' creates a pool named 'jnm-fast'.
> This seems not good until you use ns_pools list:
> ns_pools list jnm-*
> jnm-default jnm-fast
> or:
> ns_pools list [ns_info server]-*
> jnm-default jnm-fast

I really dislike this approach.  What about adding "?-server
servername?" to the API:

    ns_pools list -server foo
    default error

Also, what if you need a pool/limit that does is shared across all
servers in the entire process?  This is actually the truly useful use
case of the pools/limits mechanism--e.g., ensuring that the entire nsd
process doesn't attempt to use more than X number of threads, whatever
that X is that the physical machine can support based on its

> 5. Connection threads now are named after the threadpool being used:
> -conn:0- is now -default:0-, by default
> -conn:0- is now -jnm-fast:0- for urls which match the registration.
> The current behavior is to always use -conn:0-, -conn:1-, etc.

I *really* like this change.  Regardless of what happens to
ns_pools/ns_limits, I think this change should go in.

-- Dossy

Dossy Shiobara              | [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)

AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to