From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Christian Brunner <christian@brunner-muc.de>
Cc: Tim O'Donovan <tim@icukhosting.co.uk>, ceph-devel@vger.kernel.org
Subject: Re: Designing a cluster guide
Date: Mon, 21 May 2012 17:05:03 +0200 [thread overview]
Message-ID: <4FBA599F.5050000@profihost.ag> (raw)
In-Reply-To: <CAJafhzQp1SeGZUdUL5XszaRw-0bU0f38r3ghLgmTvZrF0oB_=w@mail.gmail.com>
Am 21.05.2012 16:59, schrieb Christian Brunner:
> Apart from that you should calculate the sum of the IOPS your guests
> genereate. In the end everything has to be written on your backend
> storage and is has to be able to deliver the IOPS.
How to measure the IOPs of a dedicated actual system?
Stefan
next prev parent reply other threads:[~2012-05-21 15:05 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 12:09 slow performance even when using SSDs Stefan Priebe - Profihost AG
2012-05-10 13:09 ` Stefan Priebe - Profihost AG
2012-05-10 18:24 ` Calvin Morrow
2012-05-10 13:23 ` Designing a cluster guide Stefan Priebe - Profihost AG
2012-05-17 21:27 ` Gregory Farnum
2012-05-19 8:37 ` Stefan Priebe
2012-05-19 16:15 ` Alexandre DERUMIER
2012-05-20 7:56 ` Stefan Priebe
2012-05-20 8:13 ` Alexandre DERUMIER
2012-05-20 8:19 ` Christian Brunner
2012-05-20 8:27 ` Stefan Priebe
2012-05-20 8:31 ` Christian Brunner
2012-05-21 8:22 ` Stefan Priebe - Profihost AG
2012-05-21 15:03 ` Christian Brunner
2012-05-20 8:56 ` Tim O'Donovan
2012-05-20 9:24 ` Stefan Priebe
2012-05-20 9:46 ` Tim O'Donovan
2012-05-20 9:49 ` Stefan Priebe
2012-05-21 14:59 ` Christian Brunner
2012-05-21 15:05 ` Stefan Priebe - Profihost AG [this message]
2012-05-21 15:12 ` Tomasz Paszkowski
[not found] ` <CANT588uxL7jrf1BfowUeer_AnDTfGjzkWVFhS4aNMaMSst_jyA@mail.gmail.com>
2012-05-21 15:36 ` Tomasz Paszkowski
2012-05-21 18:15 ` Damien Churchill
2012-05-21 20:11 ` Stefan Priebe
2012-05-21 20:13 ` Tomasz Paszkowski
2012-05-21 20:14 ` Stefan Priebe
2012-05-21 20:19 ` Tomasz Paszkowski
2012-05-21 15:07 ` Tomasz Paszkowski
2012-05-21 21:22 ` Sławomir Skowron
2012-05-21 23:52 ` Quenten Grasso
2012-05-22 0:30 ` Gregory Farnum
2012-05-22 0:42 ` Quenten Grasso
2012-05-22 0:46 ` Quenten Grasso
2012-05-22 5:51 ` Sławomir Skowron
2012-05-29 7:25 ` Quenten Grasso
2012-05-29 16:50 ` Tommi Virtanen
2012-05-22 9:04 ` Jerker Nyberg
2012-05-23 5:31 ` Gregory Farnum
2012-05-23 19:47 ` Jerker Nyberg
2012-05-23 21:47 ` Gregory Farnum
2012-05-24 8:33 ` Jerker Nyberg
2012-05-22 6:30 ` Stefan Priebe - Profihost AG
2012-05-22 6:59 ` Sławomir Skowron
2012-05-21 18:13 ` Gregory Farnum
2012-05-22 6:20 ` Stefan Priebe - Profihost AG
2012-06-29 18:07 ` Gregory Farnum
2012-06-29 18:42 ` Brian Edmonds
2012-06-29 18:50 ` Gregory Farnum
2012-06-29 20:59 ` Brian Edmonds
2012-06-29 21:11 ` Gregory Farnum
2012-06-29 21:18 ` Brian Edmonds
2012-06-29 21:30 ` Gregory Farnum
2012-06-29 21:33 ` Sage Weil
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=4FBA599F.5050000@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=christian@brunner-muc.de \
--cc=tim@icukhosting.co.uk \
/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