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 Date: Thu, 25 Aug 2005 13:50:19 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Problems with Windows threads and cygwin sleep() Message-ID: <20050825115019.GP17452@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050824185143 DOT 76C69A01 AT data DOT zone DOT ee> <430D688D DOT 1070205 AT vihmapuu DOT ee> <430D8FC8 DOT 8090906 AT vihmapuu DOT ee> <20050825100234 DOT GL17452 AT calimero DOT vinschen DOT de> <430DA017 DOT 5000402 AT vihmapuu DOT ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <430DA017.5000402@vihmapuu.ee> User-Agent: Mutt/1.4.2i On Aug 25 13:40, Raul Metsma wrote: > Seems this is something related CPU-s or total Windows thread count > I tested it on Windwos 2003, where are 2x2,4GHz Intel Xeon > There occurs this issue on 800 threads You're right, when raising the number of threads, I see this test gradually taking more CPU time the more threads it has, nearly 95% with 800 threads. As long as one starts it from a cmd shell and no Cygwin application is present, the CPU keeps low under 5%. As soon as a Cygwin process is present... Hmm. Weird. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/