Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Shankar Unni <shankar AT cotagesoft DOT com>
Subject:	Re: Percent of CPU this job got > 100%
Date:	Thu, 16 Oct 2003 10:12:12 -0700
Lines:	24
Message-ID:	<bmmjhd$mmf$1@sea.gmane.org>
References:	<bmleem$b2n$1 AT sea DOT gmane DOT org> <20031016144119 DOT GA30475 AT redhat DOT com>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (Compact)
X-Accept-Language:	en-us, en
In-Reply-To:	<20031016144119.GA30475@redhat.com>

Christopher Faylor wrote:

> On Thu, Oct 16, 2003 at 08:38:33AM +0200, Alex Vinokur wrote:

>>$ /bin/time -v a 1000
>>[...]
>> Percent of CPU this job got: 133%

> Automatic, built-in meanness at no extra charge.

:-).

Alex: is it possible your program is multi-threaded, and you have one of
those shiny new hyperthreading P4s? Remote, but that could give you this
behavior..

But even otherwise, small discrepancies between wall clock and computed
CPU clock are not uncommon, and given that your running time is pretty
close to one CPU "HZ" tick, you can get weird anomalies like this.

Try timing "a 1000000".
--
Shankar.



--
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/

- Raw text -