From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: Why the gfs2 performance regressed?
Date: Mon, 07 Jan 2008 11:48:22 +0000 [thread overview]
Message-ID: <1199706502.22038.80.camel@quoit> (raw)
In-Reply-To: <91b13c310801070148u266c0e46l1db2463ad82b9edb@mail.gmail.com>
Hi,
On Mon, 2008-01-07 at 17:48 +0800, rae l wrote:
> On Jan 3, 2008 5:36 PM, Denis Cheng <crquan@gmail.com> wrote:
> > After some bisecting work, now 2.6.22.15 is verified to be able to
> > support samba high performance, while 2.6.23 cannot,
> git bisecting work not finished, now v2.6.22 good and v2.6.23-rc1 bad.
>
> 2.6.22-g3bd858ab also good.
>
One of the patches I see in this range is:
commit 60446067ba7a8e890a91db3b4a7436fe0ebd2dee
Author: Marc Eshel <eshel@almaden.ibm.com>
Date: Mon Jan 15 18:33:36 2007 -0500
gfs2: stop giving out non-cluster-coherent leases
Now I wonder if samba is using fcntl locks rather than (incorrect, in
the clustered GFS2 case, since it doesn't support them) leases and that
is now why you are seeing the slow down. You could try (for testing
purposes only - don't do this with any important data) setting the
localflocks flag on mount and see if that makes a difference to the
speed.
If it does make a difference, then the problem is just that GFS2 doesn't
support leases in a clustered environment. If it makes no difference,
then it points more towards there being a slow-down in the I/O side,
which seems odd since my general impression is that I/O has been getting
faster recently,
Steve.
next prev parent reply other threads:[~2008-01-07 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91b13c310801012353i2f57a6c4o884b3e9aeab5970a@mail.gmail.com>
2008-01-02 10:19 ` [Cluster-devel] Re: Why the gfs2 performance regressed? Steven Whitehouse
2008-01-02 16:44 ` Cheng Renquan
2008-01-02 16:52 ` Steven Whitehouse
2008-01-03 7:27 ` Denis Cheng
2008-01-03 9:36 ` Denis Cheng
2008-01-07 9:48 ` rae l
2008-01-07 11:48 ` Steven Whitehouse [this message]
2008-01-08 7:38 ` rae l
2008-01-08 9:01 ` Steven Whitehouse
2008-01-09 10:12 ` rae l
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=1199706502.22038.80.camel@quoit \
--to=swhiteho@redhat.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.