From:	kh AT wg DOT icl DOT co DOT uk (Kevin Hughes)
Subject:	using timers causes performance limit
17 Jun 1998 14:05:49 -0700 :
Message-ID:	<01BD99F4.1C4696A0.kh.cygnus.gnu-win32@wg.icl.co.uk>
Reply-To:	"kh AT wg DOT icl DOT co DOT uk" <kh AT wg DOT icl DOT co DOT uk>
To:	"Gnuwin95 (E-mail)" <gnu-win32 AT cygnus DOT com>

Dear all,

I have noticed that my mill bound job is "throttled" when I use the "Unix" timers. If I run the job
without ever setting up a timer then I get 100% of the mill. If I set a periodic timer - using the 
setitimer function then I only get 50% of the CPU - the rest appears to be lost. By lost I mean
I don't get it nor does the system idle task. This occurs regardless of the frequency I set the
timer to - I tried 20000 microsecs and 100000 microsecs and both cause the 50% effect. What
really surprises me is that the 50% is SOLID - no variance.

I have looked at the code in windows.cc and as yet cannot see any oddities yet.

Any ideas?

Kevin

PS I am on NT4.0/SP3, Beta 19 with the latest Russian cygwin and the egcs compiler

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -