Message-Id:	<200412110251.iBB2pdfP031888@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Weird interaction between Visual C++ and Cygwin
Date:	Fri, 10 Dec 2004 20:53:31 -0600
MIME-Version:	1.0
In-Reply-To:	<00c701c4de65$98db5270$210110ac@NEEEEEEE>
X-IsSubscribed:	yes

> If any Cygwin program is running, e.g. a compilation, Visual 
> C++ takes an incredibly long time to start up.  This has been 
> the case for me for years.

*Any* cygwin program?  If I just have an rxvt terminal up with bash running,
there's no impact on any other apps.

> Does anyone know if there is some sort of locking contention here?
> 

I suspect what you're seeing is the normal "contention" of processes for CPU
time.  If you're running a build with make/gcc/binutils/etc, until the build
is done other apps have half the PC you paid for.  This is not abnormal nor
should it be unexpected.  If gcc is running full-out compiling your files,
unless you take some special action to lower its priority, the next Windows
app to come along is only going to run at "half speed".  Run another app,
and now each process gets only a third of the available processor.  Etc etc.

-- 
Gary R. Van Sickle
 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -