From: Gasper Azman <gazman@email.si>
To: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: some testing questions
Date: Mon, 14 Aug 2006 16:07:52 +0200 [thread overview]
Message-ID: <44E083B8.1030800@email.si> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1558 bytes --]
Vladimir V. Saveliev wrote:
> 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.
>
Ok. I'm gonna see about the program, and run it after each emerge --sync.
About the portage tree evolving, it's a lot (~150000) of <2k files, some
never change, and some change very often. New ones are added and old
ones deleted on a similar principle. People have been complaining for
quite some time that, while at first they experienced major speedups
regarding the operation of portage and the rsync process, it slowed to a
halt about half a year afterwards. Some blame fragmentation, and this
may be the key to diagnosing the problem.
Thanks for your help.
Gasper
[-- Attachment #1.1.2: Type: text/html, Size: 2061 bytes --]
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next reply other threads:[~2006-08-14 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 14:07 Gasper Azman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 17:44 some testing questions Gasper Azman
2006-08-14 12:15 ` Vladimir V. Saveliev
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
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=44E083B8.1030800@email.si \
--to=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.