From owner-freebsd-current@FreeBSD.ORG Thu Oct 27 08:23:29 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 384BB16A41F; Thu, 27 Oct 2005 08:23:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E16ED43D46; Thu, 27 Oct 2005 08:23:28 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 031FB46B03; Thu, 27 Oct 2005 04:23:28 -0400 (EDT) Date: Thu, 27 Oct 2005 09:23:27 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <21137.1130401220@critter.freebsd.dk> Message-ID: <20051027092153.D31152@fledge.watson.org> References: <21137.1130401220@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: David Xu , Marian Hettwer , current@freebsd.org Subject: Re: MySQL Performance 6.0rc1 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: Thu, 27 Oct 2005 08:23:29 -0000 On Thu, 27 Oct 2005, Poul-Henning Kamp wrote: > In message <43607DD5.3020708@freebsd.org>, David Xu writes: > >> Check gettimeofday syscall, it follows every I/O syscall, I think >> our gettimeofday is tooooooo expensive, if we can directly get time from >> memory, the performance will be improved further. > > Why would anybody take a timestamp at all I/O syscalls ? > > "I wonder why my car can only go 30 km/h with the trunk full of > concrete" ? > > In a data base application I could possibly understand a timestamp after > every write. > > But after _all_ I/O syscalls ? That's just plain stupid... This is actually a problem that came up with netperf as well -- it turned out we built it by default with -DHISTOGRAM, which meant that each syscall was followed by a time check. However, the issue of expensive time keeping will presumably keep coming up. It would be interesting to know which time counter is in use on the system is question. Robert N M Watson