From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Josef Bacik <jbacik@fusionio.com>,
miaox@cn.fujitsu.com
Subject: problem with ceph and btrfs patch: set journal_info in async trans commit worker
Date: Wed, 14 Nov 2012 14:42:07 +0100 [thread overview]
Message-ID: <50A39FAF.50602@profihost.ag> (raw)
Hello list,
i wanted to try out ceph with latest vanilla kernel 3.7-rc5. I was
seeing a massive performance degration. I see around 22x
btrfs-endio-write processes every 10-20 seconds and they run a long time
while consuming a massive amount of CPU.
So my performance of 23.000 iops drops to an up and down of 23.000 iops
to 0 - avg is now 2500 iops instead of 23.000.
Git bisect shows me commit: e209db7ace281ca347b1ac699bf1fb222eac03fe
"Btrfs: set journal_info in async trans commit worker" as the
problematic patch.
When i revert this one everything is fine again.
Is this known?
Greets,
Stefan
next reply other threads:[~2012-11-14 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 13:42 Stefan Priebe - Profihost AG [this message]
2012-11-15 5:18 ` problem with ceph and btrfs patch: set journal_info in async trans commit worker Miao Xie
2012-11-15 8:50 ` 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=50A39FAF.50602@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=sage@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