From: Stefan Priebe <s.priebe@profihost.ag>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: "Sébastien Han" <han.sebastien@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"Alexandre DERUMIER" <aderumier@odiso.com>
Subject: Re: improve speed with auth supported=none
Date: Tue, 13 Nov 2012 09:06:55 +0100 [thread overview]
Message-ID: <50A1FF9F.7010705@profihost.ag> (raw)
In-Reply-To: <50A1FF21.2020700@inktank.com>
Am 13.11.2012 09:04, schrieb Josh Durgin:
> On 11/12/2012 11:52 PM, Stefan Priebe wrote:
>> Am 13.11.2012 08:42, schrieb Josh Durgin:
>>> On 11/12/2012 01:57 PM, Stefan Priebe wrote:
>>>> Thanks,
>>>>
>>>> this gives another burst for iops. I'm now at 23.000 iops ;-) So for
>>>> random 4k iops ceph auth and especially the logging is a lot of
>>>> overhead.
>>>
>>> How much difference did disabling auth make vs only disabling logging?
>>
>> disable debug logging: 3000 iops
>> disable auth logging: 2000 iops
>>
>> Is anybody in the ceph team also interested in a call graph of kvm when
>> VM is doing random 4k write io?
>
> I'm interested, although I'm not sure how easy it'll be to find
> bottlenecks from it. It's worth a shot.
*arg* kvm process segfaults when i use google perf tools to create /
record one.
Any software suggestion?
Stefan
next prev parent reply other threads:[~2012-11-13 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 15:37 improve speed with auth supported=none Stefan Priebe - Profihost AG
2012-11-12 18:26 ` Sébastien Han
2012-11-12 21:57 ` Stefan Priebe
2012-11-13 7:42 ` Josh Durgin
2012-11-13 7:52 ` Stefan Priebe
2012-11-13 8:04 ` Josh Durgin
2012-11-13 8:06 ` Stefan Priebe [this message]
[not found] ` <50A39B9D.4080304@astranetwork.net>
2012-11-15 8:07 ` 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=50A1FF9F.7010705@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=han.sebastien@gmail.com \
--cc=josh.durgin@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