HP3000-L Archives

May 2003, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Wed, 21 May 2003 19:23:14 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Re:
> The Pool controls the number of JSMAIN processes.   What is the advantage of
> having two JSMAIN processes.

As Steve M said, it affects the performance during
logons.  It only comes into play during two or more
(nearly) simultaneous logon attempts.  Thus, if your
average time between logons is several minutes, you
generally won't benefit by having more than 1 spare JSMAIN.

Note that you can configure the JSMAIN pool for SESSIONS
separately from JOBS.

If you've got a **lot** of short jobs (e.g.,
averaging 5 or more jobs starting per *minute*), you
might want to increase the JOBS JSMAIN pool.
(Ditto for sessions).

In short, most people won't want more than 1 or 2.
(Ours are both 1 ... and I just noticed that the JOBS
process seems to be keeping around 2 spare JSMAINS instead
of our configured 1 :)

Stan

--
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2