T.R | Title | User | Personal Name | Date | Lines |
---|
2568.1 | An alternative | AGBEAR::HORNER | A.G.Bear, Old fashion teddy bear | Wed Apr 04 1990 11:46 | 18 |
| This would help, but is not necessarily needed. It is explained
best in the DECwindows User guide, chapter 8.
Another method that I've successfully used on 8MB 3100's is to
enable mild working set decrementing. The machines really fly
after I've done this. Here are the SYSGEN param values that
I used:
! The following 5 parameters enable working set decrementing
PFRATH=80
PFRATL=1
LONGWAIT=10
WSINC=100
WSDEC=30
Maybe they will help you too.
Dave
|
2568.2 | Why WSDEC Helps? | KYOA::PEREZ | Welcome to My Nightmare | Wed Apr 04 1990 15:52 | 10 |
|
re: .1
Can you explain why mild working set decrementing helps my
situation? Sorry, but it would help me understand the total
picture?
Thanks
Tony
|
2568.3 | 2 bit guide to client/server | DEMON3::CLEVELAND | Notes - fun or satanic cult? | Wed Apr 04 1990 17:06 | 18 |
| Working set decrementing will take memory away from inactive processes on your
workstation, and give it to those processes that are faulting heavily.
To serve DECW: ("It's a cookbook!")
1. Using session manager customize, security submenu, allow access to the
remote account that you'll use in step 2.
2. Log into that account (say, on your boot node). Do a
SET DISPLAY/CREATE/NODE=MYWS::/TRANSPORT=DECNET. Then run any DECWindows
application (Clock, Notes, etc.). It will open its window back on MYWS::
I don't think it will help matters much if all you've got for a remote host
(client in DECW terminology) is a Microvax II.
Tim
Ps: see note 1041 and 1514 for more useful information
|
2568.4 | | XUI::VANNOY | Jake VanNoy | Wed Apr 18 1990 10:43 | 5 |
| >Working set decrementing will take memory away from inactive processes on your
>workstation, and give it to those processes that are faulting heavily.
I don't think so. Working set decrementing only happens when a process hits
quantum end, and an inactive process, by defintion, doesn't hit quantum end.
|
2568.5 | Ah yes | AGBEAR::HORNER | A.G.Bear, Old fashion teddy bear | Thu Apr 19 1990 09:49 | 9 |
| .4 is right. Another trick that I do is to submit a FREEMEM job
from DECW$LOGIN.COM with a delta time far enough in the future to
let all the login activity die down. FREEMEM will purge everyone's
working set down to minimum. Those processes that are active and
need more memory will get it back. Working set decrementing helps
keep this under control. Page faults tend to stay "soft" on our
systems, so everything stays responsive.
Dave
|
2568.6 | What I've done and seems to work... | IO::MCCARTNEY | James T. McCartney III - DTN 381-2244 ZK02-2/N24 | Fri Jun 01 1990 14:03 | 8 |
| Something that I've found works well is to trim wsquota low and let
wsextent be large so that you live in overdraft most of the time.
Also, trim balsetcnt low so that you force swapping. You'll get slower
response moving from appliation to application, but it cuts down on the
paging rate while you use a single application.
James
|