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 Message-ID: <20041020134448.68649.qmail@web54308.mail.yahoo.com> Date: Wed, 20 Oct 2004 14:44:48 +0100 (BST) From: Lionel B Reply-To: cygwin AT cygwin DOT com Subject: Re: High resolution process timing To: cygwin AT cygwin DOT com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes --- Robert Pendell wrote: [top-post rearranged] > On Wed, 20 Oct 2004 12:12:37 +0100 (BST), Lionel B > Lionel B wrote: > > Greetings, > > > > Is it possible in Cygwin (W2k, Pentium 4, gcc 3.3.3) to access a higher > > resolution (or perhaps I mean "granularity") process CPU timer than the > libc > > clock() call? I am finding clock() inadequate for some code benchmarking. > > > > [It is not clear to me whether this is indeed a Cygwin issue, or rather a > > Windows issue and therefore OT here - apologies if so]. > > > > Having browsed the archives, it seems that it may well be possible to > access > > high-resolution *system* timers (perhaps using NT API calls to > > QueryPerformanceCounter() & family), but I can see no way to achieve > > per-process timing this way. > > > > Any pointers appreciated, > Search google for "windows high resolution timer" (no quotes) and that > will probably give some answers. Been there, done that. Windows high-res timers seem to boil down to QueryPerformanceCounter(), QueryPerformanceFrequency(), which measure time used by *all* (including system) processes. This is no good to me. -- Lionel B ___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com -- 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/