Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 25 Aug 2005 13:50:19 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problems with Windows threads and cygwin sleep() Message-ID: <20050825115019.GP17452@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20050824185143.76C69A01@data.zone.ee> <430D688D.1070205@vihmapuu.ee> <430D8FC8.8090906@vihmapuu.ee> <20050825100234.GL17452@calimero.vinschen.de> <430DA017.5000402@vihmapuu.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@cygwin.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/