CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: David McBride <dwm37@cam.ac.uk>
Cc: Denis Fondras <ceph@ledeuns.net>, ceph-devel@vger.kernel.org
Subject: Re: Ceph performance improvement
Date: Thu, 23 Aug 2012 15:51:35 +1200	[thread overview]
Message-ID: <5035A8C7.5050806@catalyst.net.nz> (raw)
In-Reply-To: <5034B354.1040109@cam.ac.uk>

On 22/08/12 22:24, David McBride wrote:
> On 22/08/12 09:54, Denis Fondras wrote:
>
>> * Test with "dd" from the client using CephFS :
>> # dd if=/dev/zero of=testdd bs=4k count=4M
>> 17179869184 bytes (17 GB) written, 338,29 s, 50,8 MB/s
>
> Again, the synchronous nature of 'dd' is probably severely affecting 
> apparent performance.  I'd suggest looking at some other tools, like 
> fio, bonnie++, or iozone, which might generate more representative load.
>
> (Or, if you have a specific use-case in mind, something that generates 
> an IO pattern like what you'll be using in production would be ideal!)
>
>

Appending conv=fsync to the dd will make the comparison fair enough. 
Looking at the ceph code, it does


sync_file_range(fd, offset, blocksz, SYNC_FILE_RANGE_WRITE);

which is very fast - way faster than fdatasync() and friends (I have 
tested this ... see prev posting on random write performance with file 
writetest.c attached).

I am not convinced the these sort of tests are in any way 'unfair' - for 
instance I would like to use rbd for postgres or mysql data volumes... 
and many database actions involve a stream of block writes similar 
enough to doing dd (e.g bulk row loads, appends to transaction log 
journals).

Cheers

Mark

  parent reply	other threads:[~2012-08-23  3:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  8:54 Ceph performance improvement Denis Fondras
2012-08-22 10:24 ` David McBride
2012-08-22 12:10   ` Denis Fondras
2012-08-23  3:51   ` Mark Kirkwood [this message]
2012-08-22 12:35 ` Mark Nelson
2012-08-22 12:42   ` Alexandre DERUMIER
2012-08-24 16:41   ` Denis Fondras
2012-08-24 17:42     ` Wido den Hollander
2012-08-22 16:03 ` Tommi Virtanen
2012-08-22 16:23   ` Denis Fondras
2012-08-22 16:29     ` Tommi Virtanen
2012-08-22 19:12       ` Ceph performance improvement / journal on block-dev Dieter Kasper (KD)
2012-08-22 23:19         ` Tommi Virtanen

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=5035A8C7.5050806@catalyst.net.nz \
    --to=mark.kirkwood@catalyst.net.nz \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph@ledeuns.net \
    --cc=dwm37@cam.ac.uk \
    /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