Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Dec 2001 16:24:06 -0800 (PST)
From:      Julian Elischer <julian@elischer.org>
To:        Matthew Dillon <dillon@apollo.backplane.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Seeing a lot of 'microuptime() went backwards' messages during heavy disk I/O
Message-ID:  <Pine.BSF.4.21.0112191623280.46573-100000@InterJet.elischer.org>
In-Reply-To: <200112192259.fBJMxMF90892@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I've been seeing them a lot too on a "recent" (NOV) -current


On Wed, 19 Dec 2001, Matthew Dillon wrote:

>     I'm seeing a lot of this during heavy disk I/O (5 postmark benchmarks
>     running in parallel):
> 
> microuptime() went backwards (44525.3954411 -> 44524.563978)
> microuptime() went backwards (57425.4282241 -> 57424.766121)
> microuptime() went backwards (57425.4282241 -> 57424.845844)
> microuptime() went backwards (60724.4427887 -> 60724.686232)
> microuptime() went backwards (60724.4427887 -> 60724.768808)
> microuptime() went backwards (61685.4418845 -> 61685.102724)
> microuptime() went backwards (61924.3906516 -> 61924.246151)
> microuptime() went backwards (62344.3800035 -> 62344.415407)
> 
>     Anyone know what's up?
> 
> 					-Matt
> 					Matthew Dillon 
> 					<dillon@backplane.com>
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0112191623280.46573-100000>