From: Jorge Bastos <jorge.mrbastos@gmail.com>
To: A L <mail@lechevalier.se>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.6, slow send/receive, < 1MB/s
Date: Sat, 6 Jun 2020 17:24:35 +0100 [thread overview]
Message-ID: <CAHzMYBTAnQF=+ioNx4uk1v2+0hsd+H2QujkVKAbCFgZdJF3feg@mail.gmail.com> (raw)
In-Reply-To: <CAHzMYBTpuEHRBuNNB0seKLL7D+vAdvejdT+JGTjm9c_QyrFwQw@mail.gmail.com>
Well forget that, it's not pv, it's doing it again without it, will
need to do more testing.
On Sat, Jun 6, 2020 at 5:16 PM Jorge Bastos <jorge.mrbastos@gmail.com> wrote:
>
> Hi there,
>
> Happy to report my issue is not related to btrfs, since I remembered
> reading this post and noticed performance issues after upgrading to
> kernel 5.6 wrongly assumed it was related, my issue is caused by pv,
> for some reason sometimes it starts using a lot of CPU and the
> send/receive barely crawls along, but it's not always, i.e.same
> send/receive can go at 250MB/s one time and the next time it will
> transfer at less than 10Mb/s, anyway sorry to waste everyone's time.
>
> Regards,
> Jorge Bastos
prev parent reply other threads:[~2020-06-06 16:24 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
2020-06-06 16:16 ` Jorge Bastos
2020-06-06 16:24 ` Jorge Bastos [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='CAHzMYBTAnQF=+ioNx4uk1v2+0hsd+H2QujkVKAbCFgZdJF3feg@mail.gmail.com' \
--to=jorge.mrbastos@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mail@lechevalier.se \
/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;
as well as URLs for NNTP newsgroup(s).