From: "Vladimir V. Saveliev" <vs@namesys.com>
To: reiserfs-list@namesys.com
Cc: Gasper Azman <gazman@email.si>
Subject: Re: some testing questions
Date: Mon, 14 Aug 2006 16:15:58 +0400 [thread overview]
Message-ID: <200608141615.58185.vs@namesys.com> (raw)
In-Reply-To: <44DCC20C.7020400@email.si>
Hello
On Friday 11 August 2006 21:44, Gasper Azman wrote:
> Hello everyone, especially the namesys team.
>
>
> I have been reading this list for quite some time, and saw that issues
> of fragmentation have again arisen. So, a decision was made to put the
> portage tree on a separate reiser4 partition, and to benchmark it over
> time.
>
> Because I know I'm not the smartest guy in the universe, I'm asking
> everyone here which data they would require (or want to see), how to
> obtain it (program names would suffice, but other advice will not go
> amiss) and how frequently the analysis is to be run.
reiser4progs incluses a program measurefs.reiser4. It should be able to
measure tree fragmentation. I am not sure how does portage tree evolve, but
maybe it could be interesting too see how does reiser4 tree fragmentation
change when filesystem is loaded regularly.
> Since this would be
> a new partition with nothing but the portage tree, it is an ideal and
> clean environment for testing a specific feature of reiser4 (as has been
> frequently mentioned).
>
> I hope to make a small contribution to the development of IMHO the most
> promising filesystem since ext3. :)
>
>
>
> Keep it up,
>
>
> Gasper
next prev parent reply other threads:[~2006-08-14 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 17:44 some testing questions Gasper Azman
2006-08-14 12:15 ` Vladimir V. Saveliev [this message]
2006-08-15 14:21 ` Ingo Bormuth
2006-08-15 20:04 ` Hans Reiser
2006-08-15 21:52 ` David Masover
2006-08-15 22:03 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2006-08-14 14:07 Gasper Azman
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=200608141615.58185.vs@namesys.com \
--to=vs@namesys.com \
--cc=gazman@email.si \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.