9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] new user
Date: Wed, 9 Mar 2022 23:42:16 -0500	[thread overview]
Message-ID: <CEAF1599-7B43-4E8D-A806-AB31B2560C07@stanleylieber.com> (raw)
In-Reply-To: <186AB882D78934A255DE8AD336826265@musolino.id.au>

cwfs has 16k blocks.
hjfs has 4k blocks.
this makes a huge difference if you have a large number of small files.

sl


> On Mar 9, 2022, at 11:16 PM, Alex Musolino <alex@musolino.id.au> wrote:
> 
> 
>> 
>> is it worth using hjfs vs cjfs.  Not sure of the trade off after I
>> switched?
> 
> The main benefit of hjfs(4) would seem to me to be its ability to work
> with small disks.  Running cwfs(4) on a 10GB VPS is a non-starter.  I
> think you can run cwfs(4) in a cache-only mode in such a situation,
> but then you lose the dump.  With hjfs(4) you can have it both ways.
> 
> 


  reply	other threads:[~2022-03-10  4:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27  0:11 thinktankworkspaces
2022-02-27  3:51 ` Alex Musolino
2022-02-27  3:56   ` Alex Musolino
2022-02-27  5:41   ` thinktankworkspaces
2022-03-08 13:28   ` Alex Musolino
2022-03-10  3:58     ` thinktankworkspaces
2022-03-10  4:12       ` Alex Musolino
2022-03-10  4:42         ` Stanley Lieber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-30 18:41 [9front] New user Benjamin Riefenstahl
2021-12-30 19:54 ` Humm
2022-01-01 16:56   ` Benjamin Riefenstahl
2021-12-30 20:32 ` theinicke
2021-12-30 20:45 ` ori
2021-12-30 22:00 ` qwx
2022-01-01 17:03   ` Benjamin Riefenstahl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CEAF1599-7B43-4E8D-A806-AB31B2560C07@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).