[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [patch] Add support for barriers to blk{back,front} drivers.

Gerd Hoffmann wrote:
> Ian Pratt wrote:

>> I'd certainly be interested to see some benchmarks with and without the
>> barrier support in blkfront/back.
> I'll go run some ...

I did some bonnie++ runs, each test three times.  Complete set of
results, also the scripts I've used to run stuff, are at
http://www.suse.de/~kraxel/bb/.  Handle the scripts with care, there is
a mkfs call in there ;)

I've picked two numbers (sequential block writes, sequential file
creation) which should have a bunch barrier requests for journal updates.

Machine is a intel devel box with hyperthreading, 1GB of memory, sata
disk.  I've used the ext3 filesystem, freshly created on a lvm volume,
mounted with barrier={0,1} and data=journal (to stress journaling and
barriers ...).

  wce0     -  write cache enable = off (hdparm -W0 /dev/sda)
  wce1     -  write cache enable = on  (hdparm -W1 /dev/sda)
  barrier0 -  barriers off (mount -o barrier=0)
  barrier1 -  barriers on

Here are the dom0 results:

name                   blkout   create
dom0-wce0-barrier1      12614     1841
                        12598      975
                        12575     1102
dom0-wce0-barrier0      12656     1320
                        12569     1629
                        12669     1313
dom0-wce1-barrier1      18457     2801
                        18395     3316
                        18560     2948
dom0-wce1-barrier0      19224     3190
                        18880     3079
                        19121     3555

With write caching disabled barriers don't make a big difference, it's
in the noise.  Not surprising.  With write caching enabled barriers make
things a bit slower.  But keep in mind that journaling filesystems can
NOT work reliable without barriers when write caching is enabled.  The
small performance penalty simply is the price to have to pay for
filesystem integrity.  The other way to make sure the journaling works
ok is to disable write caching.  As you can see this costs even more

domU results (guest with 256 MB memory, separate table due to the
results not being directly comparable with the dom0 ones).

name                   blkout   create
domU-wce0-barrier1       9247      866
                         9167     1265
                         9591     1131
domU-wce0-barrier0       9413      882
                         9414     1082
                         9113      942
domU-wce1-barrier1      21134     4428
                        19782     3507
                        19813     3810
domU-wce1-barrier0      20065     3411
                        20451     4342
                        20312     4672

Look simliar, but a bit more noisy, so there isn't a clear difference
visible for barriers being on/off ...


Gerd Hoffmann <kraxel@xxxxxxx>

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.