From: Stefan Priebe <s.priebe@profihost.ag>
To: Dan Van Der Ster <daniel.vanderster@cern.ch>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: default filestore max sync interval
Date: Tue, 29 Apr 2014 22:36:55 +0200 [thread overview]
Message-ID: <53600D67.1000501@profihost.ag> (raw)
In-Reply-To: <3B502314D0477C4F9478870C279E14E60118278B1F@CERNXCHG51.cern.ch>
Hi Dan,
Am 29.04.2014 22:10, schrieb Dan Van Der Ster:
> Hi all,
> Why is the default max sync interval only 5 seconds?
>
> Today we realized what a huge difference that increasing this to 30 or 60s can do for the small write latency. Basically, with a 5s interval our 4k write latency is above 30-35ms and once we increase it to 30s we can get under 10ms (using spinning disks for journal and data.)
>
> See the attached plot for the affect of this on a running cluster (the plot shows the max, avg, min write latency from a short rados bench every 10 mins). The change from 5s to 60s was applied at noon today. (And our journals are large enough, don't worry).
>
> In the interest of having sensible defaults, is there any reason not to increase this to 30s?
I was playing with them too but didn't get any viewable results. How do
you get / graph the ceph latency?
Greets,
Stefan
next prev parent reply other threads:[~2014-04-29 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 20:10 default filestore max sync interval Dan Van Der Ster
2014-04-29 20:23 ` Gregory Farnum
2014-04-29 20:35 ` Stefan Priebe
2014-04-29 20:46 ` Gregory Farnum
2014-04-29 20:36 ` Stefan Priebe [this message]
2014-04-29 20:46 ` Dan van der Ster
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=53600D67.1000501@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=daniel.vanderster@cern.ch \
/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.