All of lore.kernel.org
 help / color / mirror / Atom feed
From: A L <mail@lechevalier.se>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.6, slow send/receive, < 1MB/s
Date: Sat, 23 May 2020 18:42:27 +0200 (GMT+02:00)	[thread overview]
Message-ID: <62395bb.90271dad.172426a118f@lechevalier.se> (raw)
In-Reply-To: <CAHzMYBRMqYK4tX5eqoO95=OwZb=uqzWrUE8ngvA1rO2_gqf+Dg@mail.gmail.com>



---- From: Jorge Bastos <jorge.mrbastos@gmail.com> -- Sent: 2020-05-23 - 18:11 ----

> Hi there,
> 
> I'm also having much lower than normal send/receive performance since
> upgrading to kernel 5.6 (currently kernel 5.6.13 - btrfs-progs 5.6),
> there's also a very high CPU utilization during it, anything that can
> be done for now?
> 
> Regards,
> Jorge Bastos


One possibility is to add "mbuffer" in the pipeline. It is async compared to "pv". This helps quite a bit on spinning HDD's. 

# btrfs send /some/subvol | mbuffer | btrfs receive /other/destination

PS. There was a possibility of a bug in <=mbuffer-20150412 so don't use these old versions. 


  reply	other threads:[~2020-05-23 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  7:43 5.6, slow send/receive, < 1MB/s Chris Murphy
2020-05-04  7:47 ` Nikolay Borisov
2020-05-04  8:03 ` Chris Murphy
2020-05-04  8:12   ` Chris Murphy
2020-05-04  8:13   ` Nikolay Borisov
2020-05-04  8:25     ` Chris Murphy
2020-05-04  8:43       ` Chris Murphy
2020-05-06  5:48         ` Chris Murphy
2020-05-06 21:04           ` Chris Murphy
2020-05-06 21:07             ` Chris Murphy
2020-05-23 16:11               ` Jorge Bastos
2020-05-23 16:42                 ` A L [this message]
2020-06-06 16:16                   ` Jorge Bastos
2020-06-06 16:24                     ` Jorge Bastos

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=62395bb.90271dad.172426a118f@lechevalier.se \
    --to=mail@lechevalier.se \
    --cc=linux-btrfs@vger.kernel.org \
    /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.