Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authenticated: #14308112 Date: Thu, 25 Aug 2005 14:40:39 +0300 From: Pavel Tsekov X-X-Sender: ptsekov AT mordor To: Raul Metsma cc: cygwin AT cygwin DOT com Subject: Re: Problems with Windows threads and cygwin sleep() In-Reply-To: <430D8FC8.8090906@vihmapuu.ee> Message-ID: References: <20050824185143 DOT 76C69A01 AT data DOT zone DOT ee> <430D688D DOT 1070205 AT vihmapuu DOT ee> <430D8FC8 DOT 8090906 AT vihmapuu DOT ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Y-GMX-Trusted: 0 X-IsSubscribed: yes Hello, On Thu, 25 Aug 2005, Raul Metsma wrote: > Ohh never get this right :( > Actually I am more system administrator than programmer > > Lets try again: > http://rtedev.com/~raul/threads/threads.c > Compile this program under mingw > gcc -o threads.exe threads.c > ./threads 600 > > now compile > http://rtedev.com/~raul/threads/main.c > with cygwin > and when I execute this, then threads.exe will eat 100% CPU Ok, it happens here with 400 or more threads. The program eats CPU time when compiled with Cygwin and without Cygwin (-mno-cygwin). So this doesn't seem to be related to Cygwin but to Windows itself. I am running Windows 2000 SP4 on a PIII 1.1 Ghz with 256 Mb of ram. -- 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/