| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 189.1 | | MOVIES::LESLIE | Andy ��� Leslie | Tue Feb 14 1989 09:19 | 3 |
| I tink you'll find that less than 200 doesn't let the shareable
libraries in.
|
| 189.2 | | KONING::KONING | NI1D @FN42eq | Tue Feb 14 1989 17:26 | 9 |
| The question I would ask is: why is it set at all?
Another question: from the comments it's not clear what processes are affected
by this. Does it affect VUE tasks, for example? If so I will definitely
have to change it since I can't see any reason for having them slowed down
by such a small working set when I have memory enough.
paul
|
| 189.3 | I've seen less paging. | KNOWAY::WOLFF | Conformism is for little minds. | Tue Feb 14 1989 21:44 | 7 |
| Well since someone else raised the question, I took the liberty
to comment it out. The only effect I have seen on my 13 MB workstation
is much less paging.
Julian.
|
| 189.4 | It helps reduce memory usage | POOL::BALLOU | It's not slow, it's careful! | Wed Feb 15 1989 16:36 | 28 |
| You've got 13 MB? DROOL ... :-) (well, maybe 1/2 :-), as in "I'm gonna make
you an offer you can't refuse" :-)
The session manager process is something of an "odd bird" as far as VMS memory
management goes. It's an "active" process (meaning it does lots of work) when
you log in. But then, after it creates any DECterms and VUE session you ask
for in your configuration file, it just sits there and basically collects
broadcast messages. Now, when it's doing lots of work, there is usually
plenty of memory available for the session manager process to grow its working
set past WSQUOTA up towards WSEXTENT. Then, VMS assumes that automatic working
set adjustment will trim the process's working set downwards towards QUOTA.
However, VMS memory management does not do exceptionally well with processes
which run only infrequently and in very short spurts, as the session manager
does when it is sitting around collecting messages. Moreover, VMS memory
management prefers to deny growth of one process's working set past QUOTA
rather than take memory away from another process (on the theory that this
could lead to thrashing). Since the session manager infrequently reaches
quantum end, reducing its quota encourages the swapper to take at least the
memory "loan" made by VMS (the amount between QUOTA and EXTENT) more readily.
Otherwise, the working set of the session manager is determined by the user's
UAF record. Usually, this means the session manager ends up hoarding lots of
physical memory that could be put to better use elsewhere.
Adjusting the working set parameters of the session manager in DECW$SYLOGIN.COM
will _not_ affect those of the VUE process or any of VUE's subprocesses. The
DECterm controller and the VUE master process are created as separate jobs and
have their own working set parameters.
|
| 189.5 | | KONING::KONING | NI1D @FN42eq | Fri Feb 17 1989 11:07 | 7 |
| Thanks, that's useful information. However, it leaves another question:
does DECW$SYLOGIN.COM affect processes started by SPAWN/NOWAIT from
DECW$LOGIN.COM? I have a number of thinsg that are started that way, and
would prefer them not to be short on memory.
paul
|
| 189.6 | Here's my extra memory, I won't be needing it for a while... | RAMBLR::MORONEY | dragracing the police... | Fri Feb 17 1989 23:46 | 6 |
| re .4:
Perhaps a well-placed $PURGWS in the image might be called for...
-Mike
|
| 189.7 | Re .4: yes, subprocesses are affected | POOL::BALLOU | It's not slow, it's careful! | Mon Feb 20 1989 15:15 | 8 |
| Regarding .4:
Yes, subprocesses will inherit the working set parameters. So, you should
adjust the working set parameters after spawning whichever processes you want
to have higher quotas.
- Ken
|
| 189.8 | SPAWNed/NOWAIT restricted too!? | OIWS20::BRYSON | | Mon Feb 20 1989 15:23 | 15 |
| re: .5:
Good question. The way I understand the login process, the command
file chain is set to DECW$SYLOGIN.COM, DECW$LOGIN.COM, and then
DECW$STARTSM.COM. This means that any processes SPAWNed/NOWAIT would
not only have to share resources with the Session Manager but
that means that they would also have the working set quota restricted by
the SET WORKING_SET/QUOTA found in DECW$SYLOGIN.COM. If this is true
and the quotas restriction is primarily for the session manager,
wouldn't it be better to place the SET WORKING_SET/QUOTA in
DECW$STARTSM.COM just prior to running DECW$SESSION.EXE so that it is
the only process that is affect is the Session Manager?
David
|