From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:43:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 919B51065697; Mon, 6 Dec 2010 18:43:09 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 6D22A8FC2D; Mon, 6 Dec 2010 18:43:09 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id oB6Ih9YQ039009; Mon, 6 Dec 2010 10:43:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id oB6Ih9Gv039008; Mon, 6 Dec 2010 10:43:09 -0800 (PST) (envelope-from sgk) Date: Mon, 6 Dec 2010 10:43:09 -0800 From: Steve Kargl To: Andriy Gapon Message-ID: <20101206184309.GB38739@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CFD2A5B.1030006@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Process accounting/timing has broken recently X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 18:43:09 -0000 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