Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Marat Khalili <mkh@rqc.ru>, linux-btrfs@vger.kernel.org
Subject: Re: slow btrfs with a single kworker process using 100% CPU
Date: Wed, 16 Aug 2017 10:02:17 +0100 (BST)	[thread overview]
Message-ID: <4669553.344.1502874134710.JavaMail.gkos@dynomob> (raw)
In-Reply-To: <064eaaed-7748-7064-874e-19d270d0854e@profihost.ag>

Could be similar issue as what I had recently, with the RAID5 and 256kb chunk size.

please provide more information about your RAID setup.

p.s.
you can also check the tread "Btrfs + compression = slow performance and high cpu usage"

----- Original Message -----
From: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>
To: "Marat Khalili" <mkh@rqc.ru>, linux-btrfs@vger.kernel.org
Sent: Wednesday, 16 August, 2017 10:37:43 AM
Subject: Re: slow btrfs with a single kworker process using 100% CPU

Am 16.08.2017 um 08:53 schrieb Marat Khalili:
>> I've one system where a single kworker process is using 100% CPU
>> sometimes a second process comes up with 100% CPU [btrfs-transacti]. Is
>> there anything i can do to get the old speed again or find the culprit?
> 
> 1. Do you use quotas (qgroups)?

No qgroups and no quota.

> 2. Do you have a lot of snapshots? Have you deleted some recently?

1413 Snapshots. I'm deleting 50 of them every night. But btrfs-cleaner
process isn't running / consuming CPU currently.

> More info about your system would help too.
Kernel is OpenSuSE Leap 42.3.

btrfs is mounted with
compress-force=zlib

btrfs is running as a raid0 on top of 4 md raid 5 devices.

Greets,
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-16  9:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  6:04 slow btrfs with a single kworker process using 100% CPU Stefan Priebe - Profihost AG
2017-08-16  6:53 ` Marat Khalili
2017-08-16  8:37   ` Stefan Priebe - Profihost AG
2017-08-16  9:02     ` Konstantin V. Gavrilenko [this message]
2017-08-16  9:26       ` Stefan Priebe - Profihost AG
2017-08-16 11:48         ` Konstantin V. Gavrilenko
2017-08-16 12:00           ` Roman Mamedov
2017-08-16 12:29             ` Konstantin V. Gavrilenko
2017-08-16 12:38               ` Stefan Priebe - Profihost AG
2017-08-16 12:46               ` Stefan Priebe - Profihost AG
2017-08-16 13:04               ` Stefan Priebe - Profihost AG
2017-08-17  5:47               ` Stefan Priebe - Profihost AG
2017-08-17  7:43                 ` Stefan Priebe - Profihost AG
2017-08-20 11:00                   ` Stefan Priebe - Profihost AG
2017-08-20 12:34                     ` Marat Khalili
2017-08-28 18:09                     ` Stefan Priebe - Profihost AG
2017-08-16 23:21       ` Peter Grandi

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=4669553.344.1502874134710.JavaMail.gkos@dynomob \
    --to=k.gavrilenko@arhont.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mkh@rqc.ru \
    --cc=s.priebe@profihost.ag \
    /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