All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: Milosz Tanski <milosz@adfin.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Newstore Update Part 2
Date: Mon, 11 May 2015 10:31:44 -0500	[thread overview]
Message-ID: <5550CB60.6060002@redhat.com> (raw)
In-Reply-To: <CANP1eJEYWgp=BHh314uGqH9MAm2aW3hXgPFmVk+X4s+gQzn+HQ@mail.gmail.com>



On 05/11/2015 10:21 AM, Milosz Tanski wrote:
> On Fri, May 8, 2015 at 7: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.  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
>
>
> May I suggest that we try to test new store aging (no pun intended).
> I'm worried that inevitably we'll have cases crop up where newstore
> degrades after prolonged usage (real-world). Case like:
>
> 1) Behavior after a few TB has been written
> 2) Behavior of OSDs with newstore after it's 50% full.
> 3) Behavior after many write/del operations.
>
> I'm sure I'm missing many scenarios. We're dealing with quintessential
> filesystem design problem, how do deliver predictable performance
> after it's been used for a long time. Design maturing pains.


We do definitely need to do this, though I was hoping to wait until we 
have things a bit more stabilized since aging tests take so long to run 
and the results could change depending on if/how we handle object 
fragments for overwrites.

Mark

      reply	other threads:[~2015-05-11 15:31 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
2015-05-11 15:21 ` Milosz Tanski
2015-05-11 15:31   ` Mark Nelson [this message]

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=5550CB60.6060002@redhat.com \
    --to=mnelson@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=milosz@adfin.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.