Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jbm@eos.arc.nasa.gov (Jeffrey Mulligan)
Newsgroups: comp.sys.sun
Subject: Re: filesystem activity causes 4.0 to bog down
Keywords: SunOS
Message-ID: <2730@eos.UUCP>
Date: 8 Mar 89 15:04:50 GMT
References: <3127@pixar.UUCP>
Sender: usenet@rice.edu
Organization: NASA Ames Research Center, California
Lines: 28
Approved: Sun-Spots@rice.edu
Original-Date: 26 Feb 89 22:55:52 GMT
X-Sun-Spots-Digest: Volume 7, Issue 187, message 5 of 15

by pixar!rta@ucbvax.berkeley.edu (Rick Ace):

> 4.  Same system.
> Experimental load:  cp largefile newfile
> Now the window system bogs down real bad.  Typing ^Z in the
> window where the "cp" was running had no effect!  Trying to
> open or close other windows experienced extreme delays.
> ...Have you noticed this type of behavior on your systems?...

Since we have converted to 4.0, I have had programs become un-^Z-able,
un-^C-able.  These turned out to be 60-second core dumps.  Not
surprisingly, these problems are more severe on our 4Mb sun-3's.  It is
too bad that the system says "Segmentation error; core dumped" at the END
of the core dump, instead of saying "Segmentation violation; dumping core"
and the beginning of the core dump.  At least then you would know what was
happening.

And yes, when these core dumps are going on the window system is not
merely sluggish, it is dead to the world.

	Jeff Mulligan (jbm@aurora.arc.nasa.gov)
	NASA/Ames Research Ctr., Mail Stop 239-3, Moffet Field CA, 94035
	(415) 694-6290

[[ I don't find that surprising.  Dumping "core" is something that the
kernel does, and it tends to inhibit all normal user process activity
while it is going on.  Since a workstation has to dump to an NFS or nd
file system, it makes it only worse.  --wnl ]]