linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: "Randy.Dunlap" <rddunlap@osdlab.org>
Cc: Andrew Theurer <habanero@us.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	reiserfs-dev@namesys.com, Nikita Danilov <god@namesys.com>,
	Alexander Zarochentcev <zam@namesys.com>
Subject: Re: [reiserfs-dev] Re: Journal Filesystem Comparison on Netbench
Date: Tue, 28 Aug 2001 01:41:05 +0400	[thread overview]
Message-ID: <3B8ABE71.5FE927D2@namesys.com> (raw)
In-Reply-To: <3B8A6122.3C784F2D@us.ibm.com> <3B8AA7B9.8EB836FF@namesys.com> <3B8AB96B.A978392E@osdlab.org>

"Randy.Dunlap" wrote:
> 
> Hans-
> 
> Have you consider using OSDL machines for your testing?
> It probably wouldn't replicate Andrew's systems exactly,
> but we do have [2,4,8]-way systems that could be made
> available for your use.
> 
> ~Randy
> 
> Hans Reiser wrote:
> >
> > Please mount with -notails and repeat your results.  ReiserFS can either save
> > you on disk space, or save you on performance, but not both at the same time.
> > That said, it does not surprise me that our locking is coarser than other
> > filesystems, and we will be fixing that in version 4.  Unfortunately we don't
> > have the hardware to replicate your results.
> >
> > Hans
> >
> > Andrew Theurer wrote:
> > >
> > > Hello all,
> > >
> > > I recently starting doing some fs performance comparisons with Netbench
> > > and the journal filesystems available in 2.4:  Reiserfs, JFS, XFS, and
> > > Ext3.  I thought some of you may be interested in the results.  Below
> > > is the README from the http://lse.sourceforge.net.  There is a kernprof
> > > for each test, and I am working on the lockmeter stuff right now.  Let
> > > me
> > > know if you have any comments.
> > >
> > > Andrew Theurer
> > > IBM LTC


Ok, let's take you up on that....

we are having discussions right now of whether ReiserFS is too coarsely grained
(I argue yes based on code inspection not code measurement, others measure no
contention on a two CPU machine and say no, none of us have the hardware to
really know....)

Your hardware might help us quite a bit.

Elena, Zam, and Nikita, please email Randy off-list and make arrangements.

Hans

  reply	other threads:[~2001-08-27 21:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 15:02 Journal Filesystem Comparison on Netbench Andrew Theurer
2001-08-27 18:24 ` Journal FS Comparison on IOzone (was Netbench) Randy.Dunlap
2001-08-27 18:59   ` Brian
2001-08-27 19:28   ` Andrew Theurer
2001-08-29 16:39     ` Randy.Dunlap
2001-08-30 15:08   ` YAFB: Yet Another Filesystem Bench Yves Rougy
2001-08-27 20:04 ` Journal Filesystem Comparison on Netbench Hans Reiser
2001-08-27 20:29   ` Andrew Theurer
2001-08-27 21:19   ` Randy.Dunlap
2001-08-27 21:41     ` Hans Reiser [this message]
2001-08-28 10:05 ` Roberto Nibali
2001-08-28 15:28   ` Andrew Theurer
2001-08-28 18:38     ` Andrew Morton

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=3B8ABE71.5FE927D2@namesys.com \
    --to=reiser@namesys.com \
    --cc=god@namesys.com \
    --cc=habanero@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdlab.org \
    --cc=reiserfs-dev@namesys.com \
    --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 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).