From: Jeremy Allison <jra@samba.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Jeremy Allison <jra@samba.org>,
samba-technical@samba.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-cifs-client@lists.samba.org
Subject: Re: Samba speed
Date: Mon, 8 Dec 2008 15:12:33 -0800 [thread overview]
Message-ID: <20081208231233.GK29163@samba1> (raw)
In-Reply-To: <20081208223924.GB2501@mit.edu>
On Mon, Dec 08, 2008 at 05:39:24PM -0500, Theodore Tso wrote:
> On Mon, Dec 08, 2008 at 10:21:14AM -0800, Jeremy Allison wrote:
> > Here's a really interesting paper from Intel
> > that they recently brought to my attention.
> >
> > http://software.intel.com/en-us/articles/windows-client-cifs-behavior-can-slow-linux-nas-performance
> >
> > Looks like using XFS for your Linux Samba
> > server, or setting "strict allocate = yes" can make
> > a big difference due to sparse file issues.
>
> Glibc 2.7 (as shipped in Ubuntu Hardy) has posix_fallocate wired up to
> the fallocate system call, and ext4 supports delayed allocation as
> well as preallocation. There are number of userspace applications ---
> rsync, samba, and most bittorrent applications come to mind --- where
> use of fallocate would be a big win.
Turns out that ext4 doesn't suffer from the slowdown in the
first place. The paper is extremly interesting, I'm looking
at the implications for our default settings (most users
are still using Samba on ext3 on Linux).
Jeremy.
next prev parent reply other threads:[~2008-12-08 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 18:21 Samba speed Jeremy Allison
2008-12-08 22:39 ` Theodore Tso
2008-12-08 23:12 ` Jeremy Allison [this message]
2008-12-08 23:38 ` Theodore Tso
2008-12-09 0:37 ` Andreas Dilger
2008-12-09 6:06 ` Theodore Tso
2008-12-09 6:25 ` ronnie sahlberg
2008-12-09 6:55 ` Theodore Tso
2008-12-09 7:50 ` Volker Lendecke
2008-12-09 15:40 ` Richard Sharpe
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=20081208231233.GK29163@samba1 \
--to=jra@samba.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samba-technical@samba.org \
--cc=tytso@mit.edu \
/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).