From owner-freebsd-current Tue Apr 13 14:29:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 6496214F21 for ; Tue, 13 Apr 1999 14:29:39 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA02008; Tue, 13 Apr 1999 16:40:13 -0500 (EST) Date: Tue, 13 Apr 1999 16:40:11 -0500 (EST) From: Alfred Perlstein To: Thomas Schuerger Cc: mi@aldan.algebra.com, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: cvsup In-Reply-To: <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Apr 1999, Thomas Schuerger wrote: > > > Here's the bottom line from my point of view. CVSup is slow to update > > > the GUI because it is busy doing more important things, i.e., updating > > > your files as quickly as it can. I agree that it can be annoying. But > > > would you really want me to slow down file updates just so the GUI > > > could look better? > > > > No-no :-), please, don't... However, the CPU is not 100% busy, and > > the cvsup is still slow to update sometimes... Updating it does > > not need anything but the CPU, does it (on the local display)? > > cvsup is mostly based on disk (and network) I/O, so there shouldn't > be a problem with properly updating the GUI. Someone said it is > done in a separate process, so I still wonder why the GUI is updated > so slowly on my PII/450. My lame assumption is that modula3 uses userland threads that may be io blocking but intrupted with signals or some such if the io is blocked too long. generally i: a) use options -g -L 2 and use 'tee' to dump to a file and review that later, or b) i wait till the run is done before messing with the GUI. oh, and of course subscribe to freebsd-cvs list. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message