From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Sat May 16 18:22:16 EDT 2020
Received: from abbatoir.fios-router.home (pool-162-83-132-245.nycmny.fios.verizon.net [162.83.132.245])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 8c44e16f (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Sat, 16 May 2020 15:22:07 -0700 (PDT)
Message-ID: <D506DD1E7776D2BDFCCA29F5193E8B28@eigenstate.org>
To: jamos@oboj.net, 9front@9front.org
CC: jonas@amoson.se
Subject: Re: [9front] Plan 9 buffered IO vs APE stdio in netsurf
Date: Sat, 16 May 2020 15:22:06 -0700
From: ori@eigenstate.org
In-Reply-To: <35c584755d7907bfe42ec3b9002a7c43@oboj.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: transactional managed CSS XMPP component lifecycle control 

> Folks, I have made experiments using plan 9 buffered IO (bio) for the 
> logger in netsurf, in place of the standard APE stdio logging. If run in 
> verbose mode (-v) directing stderr to a separate window, my time from 
> start to a loaded welcome screen is down by 50% (from 2 sec to 1 sec) if 
> I run locally on my laptop. If I run over my WAN link, the startup time 
> is almost 10 times lower (from 6 min to 38 sec). The downside is that it 
> induces changes to an otherwise working upstream file 
> (nsport/netsurf/utils/log.c).
> 
> Is it worth it? I very much like bio speed, but am trying to patch the 
> upstream source as little as possible.
> 
> Jonas

It's up to you -- are you comfortable maintaining this diff against
upstream? If you are, go for it.

(The other question: why are we logging so much that this matters? Can
we shut things up, at least when not debugging?)