Date: Mon, 6 Dec 2010 10:43:09 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Process accounting/timing has broken recently Message-ID: <20101206184309.GB38739@troutmask.apl.washington.edu> In-Reply-To: <4CFD2A5B.1030006@freebsd.org> References: <20101205231829.GA68156@troutmask.apl.washington.edu> <201012060944.03196.jhb@freebsd.org> <20101206163830.GA53157@troutmask.apl.washington.edu> <201012061301.13647.jhb@freebsd.org> <4CFD2A5B.1030006@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 06, 2010 at 08:24:27PM +0200, Andriy Gapon wrote: > on 06/12/2010 20:01 John Baldwin said the following: > > Hmm, I wonder if the eventtimer stuff that has gone into HEAD recently could > > be a factor? It might change when statclock() is called. > > But I think that that code was committed more than 7-10 days ago, which Steve > mentioned. > The 7-10 days is an estimate. I upgraded world/kernel on Saturday. The previous world/kernel could have been older than I'm guessing. It could be upto 4 weeks old because my laptop tends to lag behind the upgrades to my servers. I would normally use gprof to measure execution times for the functions I'm writing, but in some quick testing last night gprof appears to be broken. I'm seeing a larger variation that I would expect in self-seconds for the accumulated time for execution of expf. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101206184309.GB38739>