From: "JP Howard" <jh_lists@fastmail.fm>
To: Chris Mason <mason@suse.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Which journal relocation+datalogging patches?
Date: Fri, 15 Nov 2002 07:43:03 +1100 [thread overview]
Message-ID: <20021114204303.CACBF5C3B9D@server5.fastmail.fm> (raw)
On 14 Nov 2002 10:10:14 -0500, "Chris Mason" <mason@suse.com> said:
> Sorry for the confusion. The journal relocation parts are in
> 01-relocation-5.diff.gz, the README was attempting to make it clear
> namesys authored it. Hopefully it is a little clearer now.
>
Perfectly clear, thankyou.
> You can use reiserfstune to change the log device of an existing disk.
> The relocation and data logging patches are considered stable, both are
> included in the suse kernels.
>
> To try the external logging device mkreisefs -j /dev/xxx -s 8192
> /dev/yyy
>
> That will create a 32MB log on /dev/xxx, and the main filesystem on
> /dev/yyy
>
Thanks for this info. I'll try this on the weekend.
> >
> > I'm really looking forward to trying this out--I plan to set aside an
> > identical server for testing and benchmarking, so hopefully we'll be able
> > to provide some interesting benchmarks of IMAP server performance with
> > external journals.
>
> Excellent, I'd love to see those numbers.
>
OK, I'll be sure to report back when we have something. That may yet take
some months--our IMAP stress test tool is not yet correctly simulating
our production profile, and is resulting in CPU bound rather than IO
bound tests. So we'll have to get that working properly first, and then
we'll be able to benchmark.
next reply other threads:[~2002-11-14 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 20:43 JP Howard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 3:30 Which journal relocation+datalogging patches? JP Howard
2002-11-14 15:10 ` Chris Mason
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=20021114204303.CACBF5C3B9D@server5.fastmail.fm \
--to=jh_lists@fastmail.fm \
--cc=mason@suse.com \
--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.