cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/5] GFS2: Bitmap search optimizations
Date: Thu, 12 Sep 2013 09:30:15 +0100	[thread overview]
Message-ID: <1378974615.2737.1.camel@menhir> (raw)
In-Reply-To: <1378925045-23318-1-git-send-email-rpeterso@redhat.com>

Hi,

This looks very good. I'll queue it just as soon as the merge window is
over so that we don't have issues around -next,

Steve.

On Wed, 2013-09-11 at 13:43 -0500, Bob Peterson wrote:
> This set of 5 patches increases the speed of GFS2's bitmap search
> algorithms. To test the performance, I added instrumentation to
> function gfs2_inplace_reserve to report the amount of time spent
> there. With the "stock" gfs2, I got 64586490 microseconds while
> running postmark with 100000 transactions and 100000 files.
> With the patched gfs2, I got 49441435, which is nearly 24% faster.
> Without the 5 GFS2 patches, postmark gave this result:
> 852.13 megabytes written (970.61 kilobytes per second)
> With the 5 patches GFS2, I got:
> 852.13 megabytes written (979.32 kilobytes per second)
> So overall, postmark performance was only 1% faster.
> Using straight dd copying 1MB files, I got 10% faster. Obviously
> mileage will vary: my hardware isn't the fastest.
> 
> The patches are as follows:
> 
> [PATCH 1/5] GFS2: optimize rbm_from_block wrt bi_start
> [PATCH 2/5] GFS2: introduce bi_blocks for optimization
> [PATCH 3/5] GFS2: Introduce rbm field bii
> [PATCH 4/5] GFS2: new function gfs2_rbm_incr
> [PATCH 5/5] GFS2: Do not reset flags on active reservations
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 




      reply	other threads:[~2013-09-12  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 18:43 [Cluster-devel] [GFS2 PATCH 0/5] GFS2: Bitmap search optimizations Bob Peterson
2013-09-12  8:30 ` Steven Whitehouse [this message]

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=1378974615.2737.1.camel@menhir \
    --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 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).