Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!shodha.enet.dec.com!alan
From: alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.)
Newsgroups: comp.unix.ultrix
Subject: Re: VAX 3100 Slow!
Summary: Characterize slow please.
Message-ID: <3058@shodha.enet.dec.com>
Date: 2 May 91 02:58:47 GMT
References: <7453@spdcc.SPDCC.COM>
Organization: Digital Equipment Corp. - Colorado Springs, CO.
Lines: 41

In article <7453@spdcc.SPDCC.COM>, jls2@spdcc.COM (Jeff Stoner) writes:
> 
> 
> I am received complaints that the VAX 3100 is "intolerably slow".
> I understand that the VAX CPU will be inherently slower than the RISC ones,
> but is there anything I can do to speed up the VAX? I don't have
> Ultrix source code, but anything else would be fair game.

	The problem is that the phrase "intolerably slow" contains
	almost no information about the system performance.  It
	could be any number of things:

	o  The system is out of memory and something as simple
	   as uniconifing a window causes it to page wildly.

	o  There is a serious system problem that is causeing the
	   system to spend large amounts of time in kernel mode.
	   For example; the error logger is busy.

	o  The one user is doing multiple things in multiple windows
	   and is running the system out of; I/O capacity and/or CPU
	   capacity.

	o  The user has a low tolerence for response time and is
	   doing a reasonable amount of work.

	The problem therefore is to find out WHY the system seems
	slow, track down the cause to and fix it.  Start by using
	cpustat, vmstat and iostat to look the time spent in various
	CPU states, the amount of available memory, the amount of
	pageing, the I/O rates on the disk drives and the load average.

	If you have Internet access consider picking up a copy of
	the program Monitor from gatekeeper.dec.com.
> 
> -- 
> ====== Jeff L. Stoner === Boulder, Colo. ============ /\ = /\ ========== |


-- 
Alan Rollow				alan@nabeth.cxn.dec.com