Subject: | |
From: | |
Reply To: | |
Date: | Thu, 4 Jan 2001 23:40:32 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
"HOFMEISTER,JAMES (HP-USA,ex1)" wrote:
> --------------------------------------------------------Donna writes--
> hi all! in our udc to start the network, there are the following
> lines....
[...snip...]
> NSCONTROL SERVER=VTSERVER,80,500
>
> is this *really* helping? ...considering it's on a 995/300 (soon to
> be a 997/400 (hehehehe))? - d
> ----------------------------------------------------------------------
>
> The feature of being able to specify the MAXIMUM number of servers
> running can be used as a tool to limit the number of servers and thus
> the performance impact of a large number of active servers...
The flip side of this is, or at least used to be, that by specifying
a MINIMUM number of servers, these processes were 'pre-launched' by
DSDAD so that incoming connections would quickly be farmed out to the
waiting but as-yet-bound daemons. This avoided the process creation
overhead and delay when establishing a new connection. In Donna's
case above, I think preloading 80 VTSERVERs is very excessive, but I
have been an advocate of having a minimum value > 0 since the classic
days.
Perhaps this is no longer a "negligable" gain by having a pool of
loaded, ready-to-go daemons at hand on today's recent MPE/iX systems?
The effect is not unlike APACHE preloading child processes to handle
http requests, except that obviously the connection rate/frequency and
persistence of said connections is an order of magnitude lower.
Jeff Kell <[log in to unmask]>
|
|
|