From owner-freebsd-hackers@FreeBSD.ORG  Fri Sep  9 16:31:34 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E04E0106566B
	for <freebsd-hackers@freebsd.org>; Fri,  9 Sep 2011 16:31:34 +0000 (UTC)
	(envelope-from dieterbsd@engineer.com)
Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67])
	by mx1.freebsd.org (Postfix) with SMTP id 8B6008FC08
	for <freebsd-hackers@freebsd.org>; Fri,  9 Sep 2011 16:31:34 +0000 (UTC)
Received: (qmail 16148 invoked by uid 0); 9 Sep 2011 16:25:38 -0000
Received: from 67.206.186.142 by rms-us016 with HTTP
Content-Type: text/plain; charset="utf-8"
Date: Fri, 09 Sep 2011 12:25:36 -0400
From: "Dieter BSD" <dieterbsd@engineer.com>
Message-ID: <20110909162537.183770@gmx.com>
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
X-Authenticated: #74169980
X-Flags: 0001
X-Mailer: GMX.com Web Mailer
x-registered: 0
Content-Transfer-Encoding: 8bit
X-GMX-UID: TksLKqAmzVK0IR3RHjUzURM/Njh6dI54
Subject: Re: excessive use of gettimeofday(2) and other syscalls
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Sep 2011 16:31:35 -0000

>> Firefox 5 and 6 has more gettimeofday call than 20000 per second on my
>> amd64-8.2-stable box.

> i don't see why chromium needs
> to call gettimeofday(2) or any library function that triggers it more
> than 3000 times a second.

What the <BLEEP> are web browsers doing that they "need" the clock
so often?

I suspect the answer is the same as why firefox uses significant amounts
of CPU when it should be idle, why it uses memory without bound
(I actually had to add ulimit to my shell's rc file :-( ), and
so on.

Using "links -g",
"ktrace -di -tc -p6951; sleep 1; ktrace -C; kdump|wc -l"
gives a typical count of 300-400, highest count seen: 1454.

What we need, is a sanely written web browser that has the
features we need. Unfortunately the last time I checked,
links and dillo both lacked features needed for online
shopping/banking.