From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil (again)
Date: Mon, 9 Jan 2012 19:44:23 -0500 [thread overview]
Message-ID: <8cf1be637c136fea77c25a1b6df9f24a@chula.quanstro.net> (raw)
In-Reply-To: <20120110024048.GA407@polynum.com>
> Side note: are there statics about the Plan9 distribution, to know what
> is the best size of blocks? It seems that there is a lot of small text
> files, so 8kb is perhaps too much.
i did these calculations for the files in / on my worm. i used values
from ken's file server for a variety of block sizes. the program is
careful to count all the indirect blocks as well, but for simplicity i
ignore directories rather than working hard to guess how much
storage they're using. (can be wrong if entries are deleted.)
i think these numbers will be similar to those of fossil.
blksize files blocks mb used
16384 35738 1427263 22300
8192 35738 2675543 20902
4096 35738 7775796 30374
obviously, there are two competing forces at work here. the amount
of space wasted off the tail of the last block, and the amount of blocks
required to map the data into the inode completely. it seems that for
my mix of files, 8k is a winner.
- erik
next prev parent reply other threads:[~2012-01-10 0:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 2:40 tlaronde
2012-01-09 22:23 ` David du Colombier
2012-01-09 22:27 ` David du Colombier
2012-01-09 22:38 ` David du Colombier
2012-01-10 17:11 ` tlaronde
2012-01-10 13:47 ` David du Colombier
2012-01-10 18:00 ` tlaronde
2012-01-13 18:33 ` tlaronde
2012-01-12 21:29 ` David du Colombier
2012-01-12 22:08 ` erik quanstrom
2012-01-12 22:25 ` David du Colombier
2012-01-12 22:37 ` erik quanstrom
2012-01-13 22:00 ` tlaronde
2012-01-10 0:44 ` erik quanstrom [this message]
2012-01-10 5:04 ` Bruce Ellis
2012-01-10 5:30 ` Lyndon Nerenberg
2012-01-10 5:34 ` Bruce Ellis
2012-01-10 17:17 ` tlaronde
2012-01-10 17:12 ` tlaronde
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=8cf1be637c136fea77c25a1b6df9f24a@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).