CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: Mark Nelson <mark.nelson@inktank.com>,
	Wido den Hollander <wido@widodh.nl>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: mon disk access pattern
Date: Fri, 15 Jun 2012 22:31:27 +0200	[thread overview]
Message-ID: <4FDB9B9F.10709@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206150930110.4551@cobra.newdream.net>

Am 15.06.2012 18:30, schrieb Sage Weil:
> On Fri, 15 Jun 2012, Mark Nelson wrote:
>> On 06/15/2012 04:51 AM, Wido den Hollander wrote:
>> I think at some point someone mentioned to me that the mon can cause a lot of
>> syncs, so running them on the OSDs without syncfs might be detrimental.  For
>> the majority of our internal performance testing I've kept them off the OSDs
>> just to be sure.
>
> Right.  The only thing interesting about the mon access pattern is that it
> calls fsync() a lot when healthy, and will call syncfs() or sync() during
> recovery.

But if i have syncfs support does it still matter if they sit on an osd 
with a seperate disk? Do you have any iops or bandwith knowledge for the 
mon daemon?

Stefan

  reply	other threads:[~2012-06-15 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15  5:52 mon disk access pattern Stefan Priebe - Profihost AG
2012-06-15  9:51 ` Wido den Hollander
2012-06-15 11:34   ` Mark Nelson
2012-06-15 16:30     ` Sage Weil
2012-06-15 20:31       ` Stefan Priebe [this message]
2012-06-18  6:39     ` Stefan Priebe - Profihost AG

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=4FDB9B9F.10709@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.com \
    --cc=sage@inktank.com \
    --cc=wido@widodh.nl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox