All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: poor write performance
Date: Sun, 21 Apr 2013 08:52:05 -0500	[thread overview]
Message-ID: <5173EF05.9000404@inktank.com> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B4D73B75D@BITCOM1.int.sbss.com.au>

On 04/19/2013 08:30 PM, James Harper wrote:
>>> rados -p <pool> -b 4096 bench 300 seq -t 64
>>
>> sec Cur ops   started  finished  avg MB/s  cur MB/s  last lat   avg lat
>>       0       0         0         0         0         0         -         0
>> read got -2
>> error during benchmark: -5
>> error 5: (5) Input/output error
>>
>> not sure what that's about...
>>
>
> Oops... I typo'd --no-cleanup. Now I get:
>
>     sec Cur ops   started  finished  avg MB/s  cur MB/s  last lat   avg lat
>       0       0         0         0         0         0         -         0
>   Total time run:        0.243709
> Total reads made:     1292
> Read size:            4096
> Bandwidth (MB/sec):    20.709
>
> Average Latency:       0.0118838
> Max latency:           0.031942
> Min latency:           0.001445
>
> So it finishes instantly without seeming to do much actual testing...

My bad.  I forgot to tell you to do a sync/flush on the OSDs after the 
write test.  All of those reads are probably coming from pagecache.  The 
good news is that this is demonstrating that reading 4k objects from 
pagecache isn't insanely bad on your setup (for larger sustained loads I 
see 4k object reads from pagecache hit up to around 100MB/s with 
multiple clients on my test nodes).

On your OSD nodes try:

sync
echo 3 > /proc/sys/vm/drop_caches

right before you run the read test.

Whatever issue you are facing is probably down at the filestore level or 
possible lower down yet.

How do your drives benchmark with something like fio doing random 4k 
writes?  Are your drives dedicated for ceph?  What filesystem?  Also 
what is the journal device you are using?

Mark

>
> James
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2013-04-21 13:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 11:46 poor write performance James Harper
2013-04-18 12:15 ` Wolfgang Hennerbichler
2013-04-18 23:11   ` James Harper
2013-04-20 10:52     ` Harald Rößler
2013-04-20 11:12       ` James Harper
2013-04-20 21:04         ` Jeff Mitchell
2013-04-18 13:43 ` Mark Nelson
2013-04-18 16:46   ` Andrey Korolyov
2013-04-18 17:01     ` Mark Nelson
2013-04-18 23:23   ` James Harper
2013-04-19  7:21     ` James Harper
2013-04-19  7:30       ` James Harper
2013-04-19 11:09         ` James Harper
2013-04-19 14:50           ` Mark Nelson
2013-04-20  0:33             ` James Harper
2013-04-20  1:30               ` James Harper
2013-04-21 13:52                 ` Mark Nelson [this message]
2013-04-22  5:32                   ` James Harper
2013-04-22 11:34                     ` Mark Nelson
2013-04-22 11:40                       ` James Harper
2013-04-21 17:56               ` Sylvain Munaut
2013-04-21 23:04                 ` James Harper
2013-04-22  8:34                   ` Sylvain Munaut
2013-04-22 11:34                     ` James Harper
2013-04-22 11:39                       ` Mark Nelson
2013-04-22 11:48                         ` James Harper
2013-04-22 12:01                           ` Mark Nelson
2013-04-22 13:47                             ` Mark Nelson
2013-04-22 15:20                         ` Sage Weil
2013-04-22 15:35                           ` Sylvain Munaut

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=5173EF05.9000404@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=james.harper@bendigoit.com.au \
    /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.