home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!hela.iti.org!cs.widener.edu!cs.widener.edu!usenet
- From: YOUNG@tattoo.cs.widener.edu (Rob Young)
- Newsgroups: comp.os.vms
- Subject: RE: Pagefile on DECram ramdisk - any comments?
- Date: 31 Dec 1992 17:44:36 GMT
- Organization: Widener News/Mail Gateway
- Lines: 49
- Distribution: world
- Message-ID: <1hvbi4INN42g@cs.widener.edu>
- References: <9212311339.AA11687@uu3.psi.com>
- NNTP-Posting-Host: tattoo.cs.widener.edu
- X-News-Reader: VMS NEWS 1.20
- In-Reply-To: leichter@lrw.com's message of 31 Dec 92 12:38:55 GMT
-
- In <9212311339.AA11687@uu3.psi.com> leichter@lrw.com writes:
-
- >
- > We are currently running a VAX 4000-300 with VMS 5.4-3. We have 128Mb
- > of memory. We currently only have one pagefile (50,000 blocks) and
- > yes, it's on the system disk (RF31). Our other two disk drives
- > (RF72's) are currently being hit so hard that a secondary pagefile on
- > those disks is not possible. I have proposed buying an RF35, but that
- > will not happen until the Fall of 1993.
- >
- > We currently have a lot of memory that is not being used (170,000+
- > blocks). Working set sizes have been tuned so folks are getting the
- > memory they deserve. I have been exploring the possibility of
- > installing a secondary pagefile on to a DECram ramdisk of say,
- > 60,000-70,000 blocks.
- >
- > Has anyone ever done this before and if so, are there any issues that
- > I should be aware of? If I make the pagefile on the ramdisk
- > sufficiently large so that it has the most Reservable pages available,
- > I should be able to ensure that the secondary pagefile is used more
- > often than not. We're running DECram v1.0, and I'm getting ready to
- > install v1.1 this week.
- >
- > Think about what you are proposing: Pages go to the pagefile when there is
- > no room for them (for whatever reason) in memory. You propose to have them
- > go to - well, memory, when there is no room in memory.
-
- [text deleted]
-
- I like Jerry's suggestion but might add what I did and you may be interested
- if you have enough time. I set a group of users WSEXTENT = WSQUOTA, started
- with a low value and bumped WSEXTENT until the user was no longer page faulting
- (or page faulting very little). I kept an eye on them with a
- show proc/cont/id=?. You *may* find a low enough WSEXTENT that
- satisfies *most* of your users. Advantage of this method is you know a
- peak WSEXTENT that you need and if you have enough memory you can set WSQUOTA
- equal WSEXTENT for everyone. Disadvantages are it is time consuming and you
- may find that certain applications bust this (i.e. tweaking results in an
- unreasonable WSEXTENT, say 16000).
-
- Have you explored the possibilty of purchasing a file cacher along the lines
- of PerfectCache? With as much memory that you have this might be a great
- solution and their prices are very reasonable.
-
- Rob
-
- young@tattoo.cs.widener.edu
- "I want to find someone on the earth so intelligent that he welcomes opinions
- which he condemns" --Chapman
-