From: Mark Nelson <mnelson@redhat.com>
To: Gregory Farnum <greg@gregs42.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Newstore Update Part 2
Date: Fri, 08 May 2015 19:52:22 -0500 [thread overview]
Message-ID: <554D5A46.7040303@redhat.com> (raw)
In-Reply-To: <CAC6JEv-thH39P9LG3ErioqzJ=MUVyWNz9_zx+Azg2aAZ+ah2yw@mail.gmail.com>
On 05/08/2015 07:19 PM, Gregory Farnum wrote:
> On Fri, May 8, 2015 at 4:21 PM, Mark Nelson <mnelson@redhat.com> wrote:
>> Hi Guys,
>>
>> At the performance meeting this week we discussed the possibility of
>> changing how newstore handles large partial overwrites.
>
> Er, what was the potential change?
Basically breaking the object up into fragments on overwrite so that we
don't do big updates to 4MB files behind the scenes. Instead for
overwrites of a certain size (say 1MB+) create a new fragment.
>
>> To determine if
>> this is useful, we look at rados bench and rbd performance of newstore at
>> various IO sizes. I've also included some rados bench read results as folks
>> were interested in those. On the graphs I've tried to mark interesting
>> improvements/regressions and also some questions/comments. These tests were
>> run without overlay which may help small IO performance in some cases.
>>
>> Graphs are here:
>>
>> http://nhm.ceph.com/newstore/8c8c5903_rbd_rados_tests.pdf
>>
>> Thanks,
>> Mark
>> --
>> 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
next prev parent reply other threads:[~2015-05-09 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 23:21 Newstore Update Part 2 Mark Nelson
2015-05-09 0:19 ` Gregory Farnum
2015-05-09 0:52 ` Mark Nelson [this message]
2015-05-11 15:21 ` Milosz Tanski
2015-05-11 15:31 ` 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=554D5A46.7040303@redhat.com \
--to=mnelson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
/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.