From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
"Mark Kampe" <mark.kampe@inktank.com>,
"Sébastien Han" <han.sebastien@gmail.com>,
"Mark Nelson" <mark.nelson@inktank.com>
Subject: Re: RBD fio Performance concerns
Date: Thu, 22 Nov 2012 16:00:27 +0100 [thread overview]
Message-ID: <50AE3E0B.8080905@profihost.ag> (raw)
In-Reply-To: <8789b7e3-daa1-4f81-88a2-59329a5c382a@mailpro>
Am 22.11.2012 15:52, schrieb Alexandre DERUMIER:
>>> I discussed this with somebody frmo inktank. Had to search the
>>> mailinglist. It might be OK if you're working with enough replicas and UPS.
>>>
>>> I see no other option while working with SSDs - the only Option would be
>>> to be able to deaktivate the journal at all. But ceph does not support this.
>
> Do you have a big difference with putting 1 journal by osd on each ssd drive ?
Not tested.
> another alternative can be (but indeed costly):
>
> - stec zeus ram ssd drive, around 2000$ for 8G (I have benched it around 100000 iops ;)
> - ddrdrive (http://www.ddrdrive.com/) (around 200000iops, don't know the price)
> - fusionio card (iodrive2, 360GB, around 3000€ , but they are 160GB model, maybe half the price)
All too expensive.
> - maybe ocz talos, around 600€ for OCZ Talos 2 R 200 Go (don't have benched them, but spec say around 35000iops random)
Not usable as each OSD can do 35.000 random IOP/s in my case and have 8
of them in each node...
Stefan
> ----- Mail original -----
>
> De: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>
> À: "Mark Nelson" <mark.nelson@inktank.com>
> Cc: "Alexandre DERUMIER" <aderumier@odiso.com>, "ceph-devel" <ceph-devel@vger.kernel.org>, "Mark Kampe" <mark.kampe@inktank.com>, "Sébastien Han" <han.sebastien@gmail.com>
> Envoyé: Jeudi 22 Novembre 2012 15:42:14
> Objet: Re: RBD fio Performance concerns
>
> Am 22.11.2012 15:37, schrieb Mark Nelson:
>> I don't think we recommend tmpfs at all for anything other than playing
>> around. :)
>
> I discussed this with somebody frmo inktank. Had to search the
> mailinglist. It might be OK if you're working with enough replicas and UPS.
>
> I see no other option while working with SSDs - the only Option would be
> to be able to deaktivate the journal at all. But ceph does not support this.
>
> Stefan
>
>> On 11/22/2012 08:22 AM, Stefan Priebe - Profihost AG wrote:
>>> Hi,
>>>
>>> can someone from inktank comment this? Might be using /dev/ram0 with an
>>> fs on it be better than tmpfs as we can use dio?
>>>
>>> Greets,
>>> Stefan
>>>
>>>> ----- Mail original -----
>>>>
>>>> De: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>
>>>> À: "Sébastien Han" <han.sebastien@gmail.com>
>>>> Cc: "Mark Nelson" <mark.nelson@inktank.com>, "Alexandre DERUMIER"
>>>> <aderumier@odiso.com>, "ceph-devel" <ceph-devel@vger.kernel.org>,
>>>> "Mark Kampe" <mark.kampe@inktank.com>
>>>> Envoyé: Jeudi 22 Novembre 2012 14:29:03
>>>> Objet: Re: RBD fio Performance concerns
>>>>
>>>> Am 22.11.2012 14:22, schrieb Sébastien Han:
>>>>> And RAMDISK devices are too expensive.
>>>>>
>>>>> It would make sense in your infra, but yes they are really expensive.
>>>>
>>>> We need something like tmpfs - running in local memory but support dio.
>>>>
>>>> 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
next prev parent reply other threads:[~2012-11-22 19:00 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50A537EA.5090409@inktank.com>
[not found] ` <CAOLwVUmQa4C_vs_Mbi3b2LeO=wx8_EMVWX5Pyu0y-JnG8nyz+Q@mail.gmail.com>
2012-11-16 22:59 ` RBD fio Performance concerns Mark Kampe
2012-11-19 14:56 ` Sébastien Han
2012-11-19 15:28 ` Alexandre DERUMIER
2012-11-19 15:42 ` Sébastien Han
2012-11-19 16:44 ` Sage Weil
2012-11-19 16:54 ` Mark Kampe
2012-11-19 18:03 ` Sébastien Han
2012-11-19 19:11 ` Alexandre DERUMIER
2012-11-19 20:57 ` Sébastien Han
2012-11-20 7:32 ` Alexandre DERUMIER
2012-11-20 10:37 ` Sébastien Han
2012-11-21 15:52 ` Mark Nelson
2012-11-21 16:34 ` Mark Nelson
2012-11-21 21:47 ` Sébastien Han
2012-11-21 22:05 ` Mark Kampe
2012-11-22 5:46 ` Alexandre DERUMIER
2012-11-23 13:36 ` Chen, Xiaoxi
2012-11-24 16:59 ` Gregory Farnum
2012-11-22 10:19 ` Stefan Priebe - Profihost AG
[not found] ` <CAOLwVUmp7wrfead8qX2BZPbyeN_JY_XBN+wkEWmbY6q1-5u0fw@mail.gmail.com>
2012-11-22 11:48 ` Stefan Priebe - Profihost AG
2012-11-22 12:50 ` Sébastien Han
2012-11-22 13:14 ` Stefan Priebe - Profihost AG
[not found] ` <CAOLwVUkwVSv-Ven2CTjnTN2J573TBTD2SLDY7df0h7ncJZQgpQ@mail.gmail.com>
2012-11-22 13:29 ` Stefan Priebe - Profihost AG
2012-11-22 14:20 ` Alexandre DERUMIER
2012-11-22 14:22 ` Stefan Priebe - Profihost AG
2012-11-22 14:37 ` Mark Nelson
2012-11-22 14:42 ` Stefan Priebe - Profihost AG
2012-11-22 14:46 ` Mark Nelson
2012-11-22 15:01 ` Stefan Priebe - Profihost AG
2012-11-22 15:26 ` Alexandre DERUMIER
2012-11-22 15:28 ` Stefan Priebe - Profihost AG
2012-11-22 15:35 ` Alexandre DERUMIER
2012-11-22 15:49 ` Sébastien Han
2012-11-22 15:54 ` Stefan Priebe - Profihost AG
2012-11-22 15:55 ` Sébastien Han
2012-11-22 15:57 ` Stefan Priebe - Profihost AG
2012-11-22 15:59 ` Stefan Priebe - Profihost AG
2012-11-22 14:52 ` Alexandre DERUMIER
2012-11-22 15:00 ` Stefan Priebe - Profihost AG [this message]
2012-11-23 10:31 ` Stefan Priebe - Profihost AG
2012-11-23 10:47 ` Alexandre DERUMIER
2012-11-23 10:49 ` Stefan Priebe - Profihost AG
2012-11-23 11:03 ` Alexandre DERUMIER
2012-11-23 13:12 ` Stefan Priebe - Profihost AG
2012-11-23 13:18 ` Mark Nelson
2012-11-23 13:24 ` Stefan Priebe - Profihost AG
2012-11-23 13:32 ` Alexandre DERUMIER
2012-11-23 13:33 ` Stefan Priebe - Profihost AG
2012-11-23 13:43 ` Stefan Priebe - Profihost AG
2012-11-22 14:34 ` Mark Nelson
[not found] ` <50AA763A.1050709@inktank.com>
2012-11-19 21:01 ` Sébastien Han
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=50AE3E0B.8080905@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=han.sebastien@gmail.com \
--cc=mark.kampe@inktank.com \
--cc=mark.nelson@inktank.com \
/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