From: Stefan Priebe <s.priebe@profihost.ag>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: massive rbd speed decrease with latest git master
Date: Mon, 05 Nov 2012 20:03:11 +0100 [thread overview]
Message-ID: <50980D6F.9010905@profihost.ag> (raw)
In-Reply-To: <50980C64.8050501@inktank.com>
Am 05.11.2012 19:58, schrieb Mark Nelson:
> On 11/05/2012 12:48 PM, Stefan Priebe wrote:
>> Am 05.11.2012 11:39, schrieb Stefan Priebe - Profihost AG:
>>> Hello list,
>>>
>>> while updating ceph to the latest master i noticed this:
>>>
>>> Commit a01b112d71a0b6a1bb206d53867d13536d17bbf6:
>>> rand. 4k WRITE: 3000 iop/s
>>>
>>> Commit 72a710ac47355ae3ca1d055be1496c91956d549d:
>>> rand. 4k WRITE: 900 iop/s
>>>
>>> Same for rand 4k read - haven't tested sequential stuff.
>>
>> OK i found out what the issue is. I get 900 iop/s when compiled with
>> syncfs support and i get 3000-6000 iop/s when compiled without syncfs
>> support.
>>
>> Strange shouldn't syncfs improve the performance?
>>
>> Note: ceph is running inside KVM right now for testing with an iscsi
>> based backend storage. My real testhw will arrive tomorrow.
>
> Very strange. I'm curious if you continue to see this on your real test
> hardware.
Yes - will report back tomorrow.
Stefan
prev parent reply other threads:[~2012-11-05 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 10:39 massive rbd speed decrease with latest git master Stefan Priebe - Profihost AG
2012-11-05 10:48 ` Stefan Priebe - Profihost AG
2012-11-05 18:48 ` Stefan Priebe
2012-11-05 18:58 ` Mark Nelson
2012-11-05 19:03 ` Stefan Priebe [this message]
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=50980D6F.9010905@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--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 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.