Date: Mon, 12 Apr 1999 22:52:52 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: schuerge@wurzelausix.CS.Uni-SB.DE Cc: current@freebsd.org Subject: Re: cvsup Message-ID: <199904130552.WAA73931@vashon.polstra.com> In-Reply-To: <199904121820.UAA09661@wurzelausix.cs.uni-sb.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199904121820.UAA09661@wurzelausix.cs.uni-sb.de>, Thomas Schuerger <schuerge@wurzelausix.CS.Uni-SB.DE> wrote: > > Is there any way to make cvsup update its GUI properly? The window > is almost dead when cvsup is performing updates, e.g. cvsup will update > the window's contents very infrequently, which is rather anoying. Perhaps > it would be a good idea to put GUI handling into a separate thread. It _is_ in a separate thread. You just need a faster CPU, or SCSI disks. :-) Running FreeBSD-3.1 with soft-updates enabled might help. Also, try the "-s" option. (Read about it first in cvsup(1).) It greatly reduces disk activity and will make your updates go faster, possibly with snappier GUI updates too. The GUI performance varies widely between systems. It was so-so on my old P/90, but it's pretty good on my PII/400. It may be the disk activity that kills the GUI performance. Disk operations are non-interruptible, so if the disk is really busy the GUI thread doesn't get control often enough. (I'm guessing and could be totally wrong, though.) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904130552.WAA73931>