From: Mark Nelson <mark.nelson@inktank.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: Amon Ott <a.ott@m-privacy.de>,
ceph-devel@vger.kernel.org,
Yann Dupont <Yann.Dupont@univ-nantes.fr>
Subject: Re: Infiniband 40GB
Date: Mon, 04 Jun 2012 07:59:58 -0500 [thread overview]
Message-ID: <4FCCB14E.6030109@inktank.com> (raw)
In-Reply-To: <70f814ae-c265-4778-bd6c-7dbbe6f9952f@mailpro>
On 6/4/12 6:40 AM, Alexandre DERUMIER wrote:
> Hi,
>
> I'm currently doing some tests with xfs, debian wheezy with standard libc6 (2.11.3-3) and 3.2 kernel.
>
> I'm doing some iostats(3 nodes with 5 osd), and I see constant writes to disks.(as the datas are flushed each second from journal to disk).
>
> Journal is big enough (20GB tmpfs) to handle 30s of write.
>
> Do you think it's related to the missing syncfs() support ?
>
> -Alexandre
Hi Alexandre,
I've included some seekwatcher results for rados bench tests using 16
concurrent 4MB writes on XFS OSD. One shows ubuntu oneiric and the
other precise (ie no syncfs support vs syncfs support in libc).
Unfortunately the original test was on 0.46 and the second test was on
0.47.2, so multiple things changed between the tests. Both were tested
with kernel 3.4. Interestingly the seeks/second don't seem to drop much
but the overall performance has about doubled. This was using a single
7200rpm disk for the OSD data disk and a seperate 7200rpm disk for the
journal in both cases. I'd definitely try 0.47.2 with a new libc though
and see how that works for you.
ceph 0.46/oneiric:
http://nhm.ceph.com/movies/mailinglist-tests/xfs-osd0-oneiric-3.4.mpg
ceph 0.47.2/precise:
http://nhm.ceph.com/movies/mailinglist-tests/xfs-osd0-precise-3.4.mpg
Mark
next prev parent reply other threads:[~2012-06-04 13:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 8:10 Infiniband 40GB Stefan Priebe
2012-06-03 12:56 ` Mark Nelson
2012-06-04 6:22 ` Hannes Reinecke
2012-06-04 7:26 ` Stefan Priebe - Profihost AG
2012-06-04 7:39 ` Hannes Reinecke
2012-06-04 7:53 ` Stefan Priebe - Profihost AG
2012-06-04 8:02 ` Hannes Reinecke
2012-06-04 8:23 ` Stefan Majer
2012-06-04 9:21 ` Yann Dupont
2012-06-04 9:35 ` Alexandre DERUMIER
2012-06-04 9:53 ` Yann Dupont
2012-06-04 9:47 ` Amon Ott
2012-06-04 9:58 ` Yann Dupont
2012-06-04 11:40 ` Alexandre DERUMIER
2012-06-04 12:59 ` Mark Nelson [this message]
2012-06-04 13:07 ` Alexandre DERUMIER
2012-06-04 13:28 ` Mark Nelson
2012-06-04 15:11 ` Gregory Farnum
2012-06-04 15:34 ` Mark Nelson
2012-06-06 16:05 ` Alexandre DERUMIER
2012-06-06 16:43 ` Mark Nelson
2012-06-04 15:42 ` Stefan Priebe
2012-06-05 7:08 ` Amon Ott
2012-06-05 7:46 ` Stefan Priebe - Profihost AG
2012-06-06 10:48 ` Stefan Priebe - Profihost AG
2012-06-06 10:57 ` Amon Ott
2012-06-06 11:02 ` Stefan Priebe - Profihost AG
2012-06-07 11:33 ` Amon Ott
2012-06-07 12:44 ` Stefan Priebe - Profihost AG
2012-06-05 8:54 ` Stefan Priebe - Profihost AG
2012-06-04 12:28 ` Mark Nelson
2012-06-04 12:34 ` Tomasz Paszkowski
2012-06-04 12:40 ` Mark Nelson
[not found] <a81f3855-1c7d-447b-9bbf-6a891e372909@mailpro>
2012-06-07 3:31 ` Alexandre DERUMIER
2012-06-07 11:25 ` Alexandre DERUMIER
2012-06-07 17:15 ` Mark Nelson
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=4FCCB14E.6030109@inktank.com \
--to=mark.nelson@inktank.com \
--cc=Yann.Dupont@univ-nantes.fr \
--cc=a.ott@m-privacy.de \
--cc=aderumier@odiso.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.