From: David Masover <ninja@slaphack.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Raymond A. Meijer" <rmeijer@internet.gr>,
reiserfs-list@namesys.com,
Alexander Zarochentcev <zam@namesys.com>
Subject: Re: reiser4 performance
Date: Mon, 08 Aug 2005 19:02:19 -0500 [thread overview]
Message-ID: <42F7F28B.7010602@slaphack.com> (raw)
In-Reply-To: <42F7D77E.5080108@namesys.com>
Hans Reiser wrote:
> David Masover wrote:
>
>
>>Raymond A. Meijer wrote:
>>
>>
>>>On Monday 8 August 2005 13:32, Hemiplegic Menehune wrote:
>>>
>>>
>>>
>>>>Its already as stable as any other fs on my systems and recovers
>>>>better than most when my battery runs out. Any idea when it will make
>>>>it into the stable 2.6 kernel?
>>>
>>>
>>>
>>>If only it had a resizer :(
>>
>>
>>Resizer isn't such a big deal. I can usually find enough backup for
>>enough of what I want, and I usually get sizes right the first time.
>>
>>What I want is the repacker, beacuse performance does steadily degrade
>>on my Reiser4 systems, eventually getting worse than Reiser3,
>
>
> I am skeptical that it gets worse than V3, unless it is because we
> haven't put in all the bitmap optimizations we did for V3. I wish I
> knew how to measure it.....
Me too. It's fairly subjective on my part, so maybe not. After all,
I've gone from lots-of-tiny-partitions to one-huge-root-partition at the
same time as I switched from v3 to v4, and I know that most of this is
probably /usr/portage. With a repacker, Reiser4 would be the best FS
for /usr/portage -- it's over a hundred thousand shell scripts and text
files which get updated usually once a day or once a week with rsync --
but without a repacker, it's best kept on a separate partition.
next prev parent reply other threads:[~2005-08-09 0:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 10:32 reiser4 performance Hemiplegic Menehune
2005-08-08 10:51 ` PFC
2005-08-08 11:09 ` Raymond A. Meijer
2005-08-08 13:38 ` Ingo Bormuth
2005-08-08 16:44 ` PFC
2005-08-08 19:53 ` David Masover
2005-08-08 20:30 ` michael chang
2005-08-08 20:34 ` michael chang
2005-08-08 20:40 ` Bedros Hanounik
2005-08-08 20:58 ` michael chang
2005-08-08 21:41 ` Ingo Bormuth
2005-08-08 20:51 ` Funding [Was:reiser4 performance] Pysiak Satriani
2005-08-08 19:56 ` reiser4 performance David Masover
2005-08-08 22:06 ` Hans Reiser
2005-08-09 0:02 ` David Masover [this message]
2005-08-09 0:16 ` michael chang
2005-08-09 1:02 ` David Masover
2005-08-09 17:52 ` michael chang
2005-08-09 20:19 ` Valdis.Kletnieks
2005-08-10 1:23 ` David Masover
2005-08-10 21:33 ` Hans Reiser
2005-08-08 18:09 ` Hans Reiser
2005-08-08 18:10 ` Hans Reiser
2005-08-08 23:13 ` Gregory Maxwell
2005-08-08 23:30 ` Hans Reiser
2005-08-09 0:20 ` David Masover
2005-08-09 0:58 ` Gregory Maxwell
2005-08-09 1:33 ` David Masover
2005-08-09 1:55 ` Gregory Maxwell
2005-08-11 18:49 ` Hans Reiser
2005-08-11 19:00 ` PFC
2005-08-11 21:29 ` Gregory Maxwell
2005-08-09 2:03 ` Gregory Maxwell
2005-08-10 1:34 ` David Masover
2005-08-10 1:51 ` Pat Double
2005-08-10 2:11 ` David Masover
2005-08-10 2:19 ` Pat Double
2005-08-10 2:32 ` David Masover
2005-08-10 2:49 ` Pat Double
2005-08-09 7:41 ` PFC
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 20:57 Pysiak Satriani
2005-08-08 22:42 ` 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=42F7F28B.7010602@slaphack.com \
--to=ninja@slaphack.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rmeijer@internet.gr \
--cc=zam@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.