From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: Intel 520/530 SSD for ceph
Date: Mon, 18 Nov 2013 14:38:42 +0100 [thread overview]
Message-ID: <528A1862.7010601@profihost.ag> (raw)
Hi guys,
in the past we've used intel 520 ssds for ceph journal - this worked
great and our experience was good.
Now they started to replace the 520 series with their new 530.
When we did we were supriced by the ugly performance and i need some
days to reproduce.
While O_DIRECT works fine for both and the intel ssd 530 is even faster
than the 520.
O_DSYNC... see the results:
~# dd if=randfile.gz of=/dev/sda bs=350k count=10000 oflag=direct,dsync
3584000000 bytes (3,6 GB) copied, 22,287 s, 161 MB/s
~# dd if=randfile.gz of=/dev/sdb bs=350k count=10000 oflag=direct,dsync
3584000000 bytes (3,6 GB) copied, 136,505 s, 26,3 MB/s
I used a blocksize of 350k as my graphes shows me that this is the
average workload we have on the journal. But i also tried using fio,
bigger blocksize, ... it stays the same.
Does anybody have an idea? Without dsync both devices have around the
same performance of 260MB/s.
Greets,
Stefan
next reply other threads:[~2013-11-18 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 13:38 Stefan Priebe - Profihost AG [this message]
[not found] ` <528A1862.7010601-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-18 22:51 ` Intel 520/530 SSD for ceph mdw-Jp3n8lUXroRWk0Htik3J/w
[not found] ` <20131118225146.GA1043-Hsy7OnahZ0C224KT6AusD78MeWzc+u9DAL8bYrjMMd8@public.gmane.org>
2013-11-19 8:02 ` Stefan Priebe
[not found] ` <528B1B21.1060203-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-21 0:29 ` mdw-Jp3n8lUXroRWk0Htik3J/w
2013-11-21 8:36 ` 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=528A1862.7010601@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.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 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.