Message-ID: <014f01c7af60$f8e818f0$0600a8c0@ze4427wm>
From: "Aaron Gray" <angray@beeb.net>
To: "Albrecht Schlosser" <cygwin@go4more.de>, <cygwin@cygwin.com>
References: <017001c7ae32$49dff3c0$0600a8c0@ze4427wm> <46728FA5.8010505@go4more.de>
Subject: Re: Cygwin allocted time slice
Date: Fri, 15 Jun 2007 16:22:22 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=response
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> Aaron Gray wrote:
> > Cygwin seems to only use a small amount of time slice relative to the 
> ammount of time slice availiable. Compiles, builds and testsuite are 
> relly slow compared to MinGW which takes too much time.
> >
> > 'time' results confirm this. Process time is about 1/4 of the total 
> system time.
> 
> Are you using a dual (or more) processor system?

No.
 
> > It i very noticable on compiling and testing GCC as compared to the 
> same on Linux or MinGW.
> 
> I assume: on (a) different machine(s) ?

Yes.
 
> > Is there any way to give Cygwin a bigger slice of the pie ?
> >
> > Say 50% or 75% ?
> 
> Well, what I saw on a dual core machine was that make seems to use only 
> one processor, and therefore I got similar CPU usage (< 50%).
> 
> Try make -j2 or make -j3 and see if you get better results. This worked 
> for me.

I will at somepoint be able to take advantage of this :)

Thanks,

Aaron


--
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/