CEPH filesystem development
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: mon disk access pattern
Date: Fri, 15 Jun 2012 11:51:35 +0200	[thread overview]
Message-ID: <4FDB05A7.3080202@widodh.nl> (raw)
In-Reply-To: <4FDACD90.2080807@profihost.ag>

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'm using a patched debian squeeze with syncfs support (thanks to amon).
> Are there any recommandations where to put the mon data? (SSD? Raid?
> Which FS?)
>

Something like a regular disk with ext4 should be fine, but you can 
always put in an SSD if you want that.

Wido

> Greets,
> Stefan
> --
> 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:[~2012-06-15  9:51 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 [this message]
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

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=4FDB05A7.3080202@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /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