All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Dawson <mdawson@gammacode.com>
To: ceph-devel@vger.kernel.org
Subject: Guidelines for Calculating IOPS?
Date: Fri, 19 Oct 2012 10:47:46 -0400	[thread overview]
Message-ID: <50816812.2040008@gammacode.com> (raw)

All,

I am investigating the use of Ceph for a video surveillance project with 
the following minimum block storage requirements:

385 Mbps of constant write bandwidth
100TB storage requirement
5250 IOPS (size of ~8 KB)

I believe 2 replicas would be acceptable. We intend to use large 
capacity (2 or 3TB) SATA 7200rpm 3.5" drives, if the IOPS work out properly.

Is there a method / formula to estimate IOPS for RDB? Specifically I 
would like to understand:

- How does replica count affect read/write IOPS?

- I'm trying to understand best practice for when to optimize server 
count, drives per server, and drive capacity as it relates to IOPS. Is 
there a point of diminishing I/O performance using server chassis with 
lots of drive slots, like the 36-drive Supermicro SC847a?


Thanks,
Mike

             reply	other threads:[~2012-10-19 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 14:47 Mike Dawson [this message]
2012-10-19 17:45 ` Guidelines for Calculating IOPS? Mark Kampe
2012-10-19 17:56   ` Wido den Hollander
2012-10-19 19:07   ` Mike Dawson
2012-10-19 20:46     ` Gregory Farnum

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=50816812.2040008@gammacode.com \
    --to=mdawson@gammacode.com \
    --cc=ceph-devel@vger.kernel.org \
    /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.