cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/2] GFS2: inplace_reserve performance improvements
Date: Fri, 28 Sep 2018 09:59:48 -0400 (EDT)	[thread overview]
Message-ID: <1019518653.16911354.1538143188726.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2750068.OGLyu1R2mJ@dhcp-3-135.uk.xensource.com>

----- Original Message -----
> I think what's happening for us is that the work that needs to be done to
> release an rgrp lock is happening pretty fast and is about the same in all
> cases, so the stats are not providing a meaningful distinction. We see the
> same lock (or small number of locks) bouncing back and forth between nodes
> with neither node seeming to consider them congested enough to avoid, even
> though the FS is <50% full and there must be plenty of other non-full rgrps.
> 
> --
> Tim Smith <tim.smith@citrix.com>

Hi Tim,

Interesting.
I've done experiments in the past where I allowed resource group glocks
to take advantage of the "minimum hold time" which is today only used for
inode glocks. In my experiments it's made no appreciable difference that I
can recall, but it might be an interesting experiment for you to try.

Steve's right that we need to be careful not to improve one aspect of
performance while causing another aspect's downfall, like improving intra-node
congestion problems at the expense of inter-node congestion.

Regards,

Bob Peterson



  reply	other threads:[~2018-09-28 13:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 14:52 [Cluster-devel] [PATCH 0/2] GFS2: inplace_reserve performance improvements Mark Syms
2018-09-20 14:52 ` [Cluster-devel] [PATCH 1/2] Add some randomisation to the GFS2 resource group allocator Mark Syms
2018-09-20 14:52 ` [Cluster-devel] [PATCH 2/2] GFS2: Avoid recently demoted rgrps Mark Syms
2018-09-20 17:17 ` [Cluster-devel] [PATCH 0/2] GFS2: inplace_reserve performance improvements Bob Peterson
2018-09-20 17:47   ` Mark Syms
2018-09-20 18:16     ` Steven Whitehouse
2018-09-28 12:23     ` Bob Peterson
2018-09-28 12:36       ` Mark Syms
2018-09-28 12:50         ` Mark Syms
2018-09-28 13:18           ` Steven Whitehouse
2018-09-28 13:43             ` Tim Smith
2018-09-28 13:59               ` Bob Peterson [this message]
2018-09-28 14:11                 ` Mark Syms
2018-09-28 15:09                 ` Tim Smith
2018-09-28 15:09               ` Steven Whitehouse
2018-09-28 12:55         ` Bob Peterson
2018-09-28 13:56           ` Mark Syms
2018-10-02 13:50             ` Mark Syms

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=1019518653.16911354.1538143188726.JavaMail.zimbra@redhat.com \
    --to=rpeterso@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 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).