On Aug 25 14:59, Pavel Tsekov wrote: > Hello, > > On Thu, 25 Aug 2005, Corinna Vinschen wrote: > > > 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... > > Here when the app is compiled with -mno-cygwin it takes 100% cpu when it > allocates 400+ threads - both from Windows Command Prompt and Cygwin bash. > After all the testcase consist almost entirely of Win32 calls.
You're on W2K, I'm on XP, maybe there's a difference? I can easily reproduce nearly 0% CPU with 1000 threads if no Cygwin process is present and nearly 99% if a Cygwin process is present. Even if we can't do much about it, it would be interesting to find out how Cygwin affects CPU usage of non-Cygwin processes. 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/