From: "darren" <teodarren@myrealbox.com>
To: "'Hans Reiser'" <reiser@namesys.com>,
"'Ragnar Kjorstad'" <reiserfs@ragnark.vestdata.no>
Cc: 'reiserfs' <reiserfs-list@namesys.com>, 'Mike Jadon' <mikej@umem.com>
Subject: RE: reiserfs vs NTFS vs WAFL
Date: Thu, 22 May 2003 22:39:56 +0800 [thread overview]
Message-ID: <003b01c32070$052d59b0$0101a8c0@bummer> (raw)
In-Reply-To: <3ECBC1DF.3060607@namesys.com>
Hi all,
Thanx for replying to my mail.
I am doing some tests on this three FS now (to see if we would want to
spend $$$$$ on a netapp).
My test is based on the simultaneous creation and deletion of small
files 50Kb, as per my actual usage of the file server for my application
servers.
My main problem with using Linux/Reiserfs3 is with the performance of
Samba when under heavy load. CIFS operation is required as some of our
application servers are windows based. Netapp's CIFS performance is
really incredible.
With NFS, we can sometimes beat the netapp F87 with a
Linux/ReiserFs/RAID0 config with the same number of harddisk.
Will post more details when I thru with it.
In the mean time, will really appreciate any suggestions to improving
Samba's performance in order to make a CIFS file server based on
Linux/Reiser/Samba possible.
-----Original Message-----
From: Hans Reiser [mailto:reiser@namesys.com]
Sent: Thursday, May 22, 2003 2:14 AM
To: darren
Cc: 'reiserfs'; Mike Jadon
Subject: Re: reiserfs vs NTFS vs WAFL
darren wrote:
>Hi all,
>
>I wonder if there are any papers or benchmarks that compare the
>performance and architectural differences between reiserfs, NTFS and
>WAFL (NetApp's Write Anywhere File Layout)?
>
>Any help will be great.
>
>Regards
>darren
>
>
>
>
>
I regret to say that all I can do is point you to my LinuxTag paper at
www.namesys.com/v4/reiser4_the_atomic_filesystem.html, and give you my
informal opinion that NTFS sucks but has improved a lot, and WAFL is
great for NFS.
I'd be curious to see mongo numbers on NTFS if anyone has the energy.
Most people comparing WAFL and ReiserFS look at the price per GB and we
win without the benchmark ever being run. mp3.com for instance
sponsored us so that they could save $22 million on Netapps and Suns.
I would expect WAFL to beat Linux/NFS/ReiserFS V3/RAID because that is
their niche and they are sharp and I bet their zero copy NFS code is
better than Linux's, but no one knows for real. I would be curious to
see Reiser4 benchmarked against WAFL when we are done, especially if you
toss in some cards from umem that Mike sells. ReiserFS might save some
disk space compared to WAFL.
I would expect NetApp to just blow away any NTFS server.... but I
haven't measured it.
--
Hans
next prev parent reply other threads:[~2003-05-22 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 19:31 Performance figures with and without relocated journal Philippe Gramoullé
2003-05-21 8:59 ` Edward Shushkin
2003-05-21 14:13 ` reiserfs vs NTFS vs WAFL darren
2003-05-21 18:13 ` Hans Reiser
2003-05-22 14:39 ` darren [this message]
2003-05-22 15:25 ` Hans Reiser
2003-05-23 13:07 ` darren
2003-05-22 17:07 ` Ragnar Kjørstad
2003-05-22 17:22 ` Hans Reiser
2003-05-22 17:44 ` Ragnar Kjørstad
2003-05-23 13:15 ` darren
2003-05-22 10:55 ` Ragnar Kjørstad
2003-05-24 5:35 ` Heinz-Josef Claes
2003-06-03 17:59 ` 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='003b01c32070$052d59b0$0101a8c0@bummer' \
--to=teodarren@myrealbox.com \
--cc=mikej@umem.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=reiserfs@ragnark.vestdata.no \
/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.