All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim Schutt" <jaschut@sandia.gov>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: leveldb compaction overhead
Date: Fri, 31 May 2013 15:31:26 -0600	[thread overview]
Message-ID: <51A916AE.9010700@sandia.gov> (raw)
In-Reply-To: <alpine.DEB.2.00.1305291406080.16097@cobra.newdream.net>

Hi Sage,

On 05/29/2013 03:07 PM, Sage Weil wrote:
> Hi all-
> 
> I have a couple of branches (wip-5176 and wip-5176-cuttlefish) that try to 
> make the leveldb compaction on the monitor less expensive by doing it in 
> an async thread and compaction only the trimmed range.  If anyone who is 
> experience high monitor io on cuttlefish would like to test it out, 
> feedback on whether/how much it improves things would be much appreciated!

I've been flogging wip-5176-cuttlefish merged into recent cuttlefish
branch (commit 02ef6e918e), and the result has been very stable for
me.  I've been testing OSD reweights, and so have been getting lots
of pgmap updates, and lots of data movement.

I'm no longer seeing stalls, and I see much less data movement
on the monitor hosts.  I haven't seen any monitors drop out
and rejoin, which had been a regular occurrence for me.
I stopped a mon and reinitialized it, and it resync'ed in 
just a few minutes, which is also a big improvement.

This is all with 128K PGs - next week I'll try much higher
PG counts.

Thanks a bunch for these fixes - they are working great
for me!

Thanks -- Jim

> 
> Thanks-
> sage
> --
> 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-05-31 21:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 21:07 leveldb compaction overhead Sage Weil
2013-05-31 21:31 ` Jim Schutt [this message]
2013-06-01  0:00   ` Sage Weil
2013-06-05 19:00     ` Jim Schutt
2013-06-05 19:05       ` Mark Nelson
2013-06-05 19:16         ` Jim Schutt

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=51A916AE.9010700@sandia.gov \
    --to=jaschut@sandia.gov \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.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.