Date: Thu, 6 Jul 2000 21:37:19 -0400 From: Bill Fumerola <billf@chimesnet.com> To: Alfred Perlstein <bright@wintelcom.net> Cc: Marius Bendiksen <mbendiks@eunet.no>, freebsd-arch@FreeBSD.ORG Subject: Re: Alterations to vops Message-ID: <20000706213719.X4034@jade.chc-chimes.com> In-Reply-To: <20000706160120.Z25571@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Jul 06, 2000 at 04:01:20PM -0700 References: <20000628231510.F275@fw.wintelcom.net> <Pine.BSF.4.05.10007062327020.68909-100000@login-1.eunet.no> <20000706173234.V4034@jade.chc-chimes.com> <20000706160120.Z25571@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 06, 2000 at 04:01:20PM -0700, Alfred Perlstein wrote: > > My systems get to the point of unusability when find(1) or cvsup(1) are > > running. These things should be getting scheduled way back, but when > > I hit 'i' in vi, it can take 30 seconds for it to switch to insert mode. > > > > These are not wimpy machines either. > > The disks are busy and vi most likely is doing an IO request, either > implement a per-process buffer high water mark or deal with it. :) There was a time when this didn't happened. Part of me wants to think "oh, FreeBSD is just more efficient at saturating the I/O bus" but the other part of me says "damnit, I don't give a shit how long cvsup takes or the nightly output run takes, but I would like to edit files sometime today." -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000706213719.X4034>