All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Andrew Martin <amartin@xes-inc.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Performance testing with bcache
Date: Sat, 15 Mar 2014 17:52:15 +0000	[thread overview]
Message-ID: <20140315175212.GA20197@sucs.org> (raw)
In-Reply-To: <1899882151.50322.1394831787760.JavaMail.zimbra@xes-inc.com>

On Fri, Mar 14, 2014 at 04:16:27PM -0500, Andrew Martin wrote:
> 
> Do you have an example fio job file that has worked well for testing
> bcache?

Try these as a starting point:
benchmark-seq.fio:
; Script to gather general sequential write performance statistics
; Basic usage:
; BS="4k" DEV="sdf" RT=90 SEED=21 TYPE="ssd" fio benchmark-seq.fio

[global]
filename=/dev/${DEV}
runtime=${RT}
bs=${BS}
iodepth=4
ioengine=libaio
direct=1
stonewall
size=${SIZE}
randseed=${SEED}
[write]
rw=write

benchmark-rand.fio:
; Script to gather general random write performance statistics
; Basic usage:
; BS="4k" DEV="sdf" RT=90 SEED=21 TYPE="ssd" fio benchmark-rand.fio

[global]
filename=/dev/${DEV}
runtime=${RT}
bs=${BS}
iodepth=4
ioengine=libaio
direct=1
stonewall
size=${SIZE}
randseed=${SEED}
[randwrite]
rw=randwrite

After making the above files do
export RT=30; export SEED=21; export SIZE="10G"; export DEV="bcache0"
for b in "4" "16" "64"; do export BS="${b}k"; for job in "benchmark-seq" "benchmark-rand"; do fio $job.fio; done; done

The first time round get the stats where the cache is not being used.
Next time round set the appropriate cache options (easier said than done
:-), run a single benchmark-seq.fio job (I'd recommend 64k blocksize) to
warm the cache then rerun the above.

Let us know what you did and how it went!

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2014-03-15 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <155722734.53464.1394740311695.JavaMail.zimbra@xes-inc.com>
2014-03-13 20:12 ` Performance testing with bcache Andrew Martin
2014-03-13 20:53   ` Sitsofe Wheeler
2014-03-14 18:41     ` Andrew Martin
2014-03-14 21:16       ` Andrew Martin
2014-03-15 17:52         ` Sitsofe Wheeler [this message]
2014-04-04 17:06           ` Andrew Martin
2014-04-04 19:10             ` Kent Overstreet
2014-04-05  7:57               ` Sitsofe Wheeler

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=20140315175212.GA20197@sucs.org \
    --to=sitsofe@yahoo.com \
    --cc=amartin@xes-inc.com \
    --cc=linux-bcache@vger.kernel.org \
    /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.