home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: vmsnet.internals
- Path: sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!news.ysu.edu!malgudi.oar.net!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!pa.dec.com!ripple.enet.dec.com!pettigrew_mi
- From: pettigrew_mi@ripple.enet.dec.com (Mike Pettigrew)
- Subject: Re: RE: VMS tuning for a vaxcluster (LAVC)
- Message-ID: <1992Aug28.175448.5429@PA.dec.com>
- Sender: news@PA.dec.com (News)
- Organization: Digital Equipment Corporation
- References: <9208281401.AA18734@sndsu1.sinet.slb.com>
- Date: 28 AUG 92 10:09:23 PDT
- Lines: 54
-
-
- In article <9208281401.AA18734@sndsu1.sinet.slb.com>, brydon@dsny25.sinet.slb.com writes...
-
- >
- >My claim is that paging through [an unloaded] ethernet is faster than to a
- >local disk. Of course if a lot of systems page this way, you will have a
- >network contention problem which will slow things down. [By the way, this
- >assumes paging to another VMS system. Paging to an Infoserver, as per the
- >VXT2000 workstation is essentially the speed of the disk on the infoserver,
- >plus you are generating ethernet traffic. There is no caching on an
- >Infoserver.]
- >
- >Any disagreements with the above? Anybody do any quantitative testing on
- >this?
-
-
- Experiments with a production system of approximately 120 VAXstations on
- a LAVC, show that local page and swap files consistently offer better
- performance than paging or swapping to disks on the server.
-
- Caching adjustments on the server, beyond the defaults computed by AUTOGEN
- did not appear to have a critical effect on performance.
-
- What does have a very critical effect is changes to the system parameters
- WSMAX, MPW_HILIMIT, PQL_MWSQUOTA, PQL_MWSEXTENT , and also changes to the
- SYSUAF field WSEXTENT. On a memory-rich system, these fields can be raised
- to much higher values than the default calculations.
-
- The practical effect of raising these parameters is to eliminate paging
- and swapping activity on the sattelite nodes althogether.
-
- If you INSTALL all of the images that you are using on the sattelite nodes,
- and keep a free list of about 4,000 pages, you will rapidly have all of
- the relavent system image pages cached in the free list at the sattelite
- node.
-
- Ethernet bandwidth is comparable to the disk transfer speeds, thus light
- access to COM files and incidental data files is as fast from the server
- as it is from a local disk. If you have lots of users, and your applications
- have many COM files, you will run into problems with seek contention, and
- should consider local disks. If you have an application that uses many data
- files or is I/O intensive, you will have seek and bandwidth contention, and
- again should consider local disks.
-
- ----------------------------------------------------------------------------
- | -Mike Pettigrew pettigrew_mi@ripple.enet.dec.com
- | (206) 661-3032
- | Digital Equipment Corporation
- | Federal Way, Washington, USA
- |___________________________________________________________________________
- | Surprises Every Day!
- |___________________________________________________________________________
- |These opinions are mine and not necessarily my employer's
- ----------------------------------------------------------------------------
-