From: Mark Nelson <mnelson@redhat.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Initial newstore vs filestore results
Date: Thu, 09 Apr 2015 12:00:52 -0500 [thread overview]
Message-ID: <5526B044.2090002@redhat.com> (raw)
In-Reply-To: <5525EFCC.3070607@redhat.com>
On 04/08/2015 10:19 PM, Mark Nelson wrote:
> On 04/07/2015 09:58 PM, Sage Weil wrote:
>> What would be very interesting would be to see the 4KB performance
>> with the defaults (newstore overlay max = 32) vs overlays disabled
>> (newstore overlay max = 0) and see if/how much it is helping.
>
> And here we go. 1 OSD, 1X replication. 16GB RBD volume.
>
> 4MB write read randw randr
> default overlay 36.13 106.61 34.49 92.69
> no overlay 36.29 105.61 34.49 93.55
>
> 128KB write read randw randr
> default overlay 1.71 97.90 1.65 25.79
> no overlay 1.72 97.80 1.66 25.78
>
> 4KB write read randw randr
> default overlay 0.40 61.88 1.29 1.11
> no overlay 0.05 61.26 0.05 1.10
>
Update this morning. Also ran filestore tests for comparison. Next
we'll look at how tweaking the overlay for different IO sizes affects
things. IE the overlay threshold is 64k right now and it appears that
128K write IOs for instance are quite a bit worse with newstore
currently than with filestore. Sage also just committed changes that
will allow overlay writes during append/create which may help improve
small IO write performance as well in some cases.
4MB write read randw randr
default overlay 36.13 106.61 34.49 92.69
no overlay 36.29 105.61 34.49 93.55
filestore 36.17 84.59 34.11 79.85
128KB write read randw randr
default overlay 1.71 97.90 1.65 25.79
no overlay 1.72 97.80 1.66 25.78
filestore 27.15 79.91 8.77 19.00
4KB write read randw randr
default overlay 0.40 61.88 1.29 1.11
no overlay 0.05 61.26 0.05 1.10
filestore 4.14 56.30 0.42 0.76
Seekwatcher movies and graphs available here:
http://nhm.ceph.com/newstore/20150408/
Note for instance the very interesting blktrace patterns for 4K random
writes on the OSD in each case:
http://nhm.ceph.com/newstore/20150408/filestore/RBD_00004096_randwrite.png
http://nhm.ceph.com/newstore/20150408/default_overlay/RBD_00004096_randwrite.png
http://nhm.ceph.com/newstore/20150408/no_overlay/RBD_00004096_randwrite.png
Mark
next prev parent reply other threads:[~2015-04-09 17:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 14:57 Initial newstore vs filestore results Mark Nelson
2015-04-07 19:16 ` Mark Nelson
2015-04-08 1:45 ` Mark Nelson
2015-04-08 1:48 ` Somnath Roy
2015-04-08 1:53 ` Mark Nelson
2015-04-08 2:26 ` Chen, Xiaoxi
2015-04-08 2:58 ` Sage Weil
2015-04-08 7:24 ` Haomai Wang
2015-04-08 16:49 ` Sage Weil
2015-04-08 17:19 ` Gregory Farnum
2015-04-08 17:38 ` Sage Weil
2015-04-08 19:16 ` Milosz Tanski
2015-04-08 14:38 ` Mark Nelson
2015-04-09 3:19 ` Mark Nelson
2015-04-09 17:00 ` Mark Nelson [this message]
2015-04-10 6:11 ` Duan, Jiangang
2015-04-10 10:25 ` Ning Yao
2015-04-10 15:28 ` Sage Weil
2015-04-10 15:53 ` Mark Nelson
2015-04-10 19:41 ` Mark Nelson
2015-04-10 20:04 ` Mark Nelson
2015-04-10 23:24 ` Sage Weil
2015-04-10 23:44 ` Duan, Jiangang
2015-04-10 23:58 ` Mark Nelson
2015-04-10 23:43 ` Duan, Jiangang
2015-04-11 0:09 ` Mark Nelson
2015-04-11 13:22 ` Duan, Jiangang
2015-04-10 12:07 ` Mark Nelson
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=5526B044.2090002@redhat.com \
--to=mnelson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.