All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Wido den Hollander <wido@widodh.nl>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: mon disk access pattern
Date: Mon, 18 Jun 2012 08:39:38 +0200	[thread overview]
Message-ID: <4FDECD2A.5090607@profihost.ag> (raw)
In-Reply-To: <4FDB1DCC.6090701@inktank.com>

Am 15.06.2012 13:34, schrieb Mark Nelson:
> On 06/15/2012 04:51 AM, Wido den Hollander wrote:
>> Hi,
>>
>> On 15-06-12 07:52, Stefan Priebe - Profihost AG wrote:
>>> Hello list,
>>>
>>> i read somewhere that the mon has "special" disk access patterns - even
>>> though it does not write much data.
>>
>> "special"? Where did you read that? The monitor has about 1 ~ 2GB of
>> storage.
>>
>> So if your monitor has something like 4GB ~ 8GB of RAM, your kernel
>> should cache almost all your monitor data.
>>
>
> 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.

My main idea behind that was what type of disk i need for a performant 
mon system. SATA, SAS, SSD? Raid?

Stefan

      parent reply	other threads:[~2012-06-18  6:39 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
2012-06-18  6:39     ` Stefan Priebe - Profihost AG [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=4FDECD2A.5090607@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@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 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.