Date: Mon, 06 Dec 2010 21:00:54 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: Process accounting/timing has broken recently Message-ID: <4CFD32E6.7040003@FreeBSD.org> In-Reply-To: <20101206184949.GA39028@troutmask.apl.washington.edu> 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> <20101206184309.GB38739@troutmask.apl.washington.edu> <4CFD2F77.8020409@freebsd.org> <20101206184949.GA39028@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06.12.2010 20:49, Steve Kargl wrote: > On Mon, Dec 06, 2010 at 08:46:15PM +0200, Andriy Gapon wrote: >> on 06/12/2010 20:43 Steve Kargl said the following: >>> 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 see. >> >>> 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. >> >> Just guessing - could you try setting sysctl kern.eventtimer.periodic=1 if it's >> not 1 already? >> >> And cc-ing Alexander, just in case. > > Thanks for the suggestion. I'll try this tonight (I left the > laptop at home) and will report back here. Unless your application utilizes all CPUs all the time, you can also try to set sysctl kern.eventtimer.idletick=1. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CFD32E6.7040003>