All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: miaox@cn.fujitsu.com
Cc: Sage Weil <sage@inktank.com>,
	"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>
Subject: Re: problem with ceph and btrfs patch: set journal_info in async trans commit worker
Date: Thu, 15 Nov 2012 09:50:29 +0100	[thread overview]
Message-ID: <50A4ACD5.9050809@profihost.ag> (raw)
In-Reply-To: <50A47B16.6040308@cn.fujitsu.com>

Hi Miao,

Am 15.11.2012 06:18, schrieb Miao Xie:
> Hi, Stefan
>
> On wed, 14 Nov 2012 14:42:07 +0100, Stefan Priebe - Profihost AG wrote:
>> 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?
>
> Could you try the following patch?
>
> http://marc.info/?l=linux-btrfs&m=135175512030453&w=2
>
> I think the patch
>
>    Btrfs: set journal_info in async trans commit worker
>
> is not the real reason that caused the regression.
>
> I guess it is caused by the bug of the reservation. When we join the
> same transaction handle more than 2 times, the pointer of the reservation
> in the transaction handle would be lost, and the statistical data in the
> reservation would be corrupted. And then we would trigger the space flush,
> which may block your tasks.

i applied your whole patchset. It looks a lot better now but avg iops is 
now 5000 iops and not 23.000 like when removing the mentioned commit 
(e209db7ace281ca347b1ac699bf1fb222eac03fe).

Stefan

      reply	other threads:[~2012-11-15  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 13:42 problem with ceph and btrfs patch: set journal_info in async trans commit worker Stefan Priebe - Profihost AG
2012-11-15  5:18 ` Miao Xie
2012-11-15  8:50   ` Stefan Priebe - Profihost AG [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=50A4ACD5.9050809@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 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.