From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.oboj.net ([195.178.185.14]) by ewsd; Sat May 16 06:02:33 EDT 2020 Received: from localhost (localhost [127.0.0.1]) by mail.oboj.net (Postfix) with ESMTP id C4BF7BC5D60; Sat, 16 May 2020 12:02:18 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.oboj.net Received: from mail.oboj.net ([127.0.0.1]) by localhost (mail.oboj.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1TVvkTq4MPPm; Sat, 16 May 2020 12:02:18 +0200 (CEST) Received: from www.oboj.net (unknown [195.178.185.23]) by mail.oboj.net (Postfix) with ESMTP id 2B327BC5D5C; Sat, 16 May 2020 12:02:18 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 16 May 2020 13:02:17 +0300 From: jamos@oboj.net To: 9front@9front.org Cc: jonas@amoson.se Subject: Plan 9 buffered IO vs APE stdio in netsurf Message-ID: <35c584755d7907bfe42ec3b9002a7c43@oboj.net> X-Sender: jamos@oboj.net User-Agent: Roundcube Webmail/1.3.4 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: table persistence event-oriented pipelining interface 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