From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from 199.241.189.110 ([199.241.189.110]) by ttr; Tue Aug 26 12:03:35 EDT 2014
Date: Tue, 26 Aug 2014 12:03:31 -0400
From: sl@9front.org
To: 9front@9front.org
Subject: Re: [9front] cwfs and hjfs
Message-ID: <4d70f8b91dbc85a44c6106251cb98ec8@xx230.inri>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: managed information browser-scale grid framework
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

> I replaced this by SanDisk SDHC 4GB sd card.
> it improved the speed high.   However, it is
> still slow for me.
> To use Japanese, I use ktrans, and the speed is
> very slow.   It takes 2 to 3 seconds after I hit 
> transkation key.   Also, it is difficult to acquire
> update by hg, where it stops on its work.
> 
> I'd like to use cwfs on this SD card pi.

Hi Kenji,

In fqa4[0] we recommend at least 12GB for a cwfs installation. By default,
cwfs uses 16KB blocks and creates three separate subdivisions within the Plan 9
partition (worm, other, fscache), which ends up requiring more working space
than hjfs with it's 4KB blocks and single partition. At 4GB you may run out
of space fairly quickly after rebuilding the system and periodic dumps are
taken into account.

It also seems unlikely that file system speed is really your bottleneck. I used
the rpi tcp booted (no local disk access after boot) and experienced similar
problems. The USB ethernet seems to tax the system severely: when the network
was active I routinely experienced dropouts in typing on my USB keyboard. This
could also be related to voltage.

For what it's worth, the cat-v.org sites run on hjfs (at ramnode.com, KVM
backed by an SSD).

sl

[0] http://code.google.com/p/plan9front/wiki/fqa4#4.3.6_-_configfs