ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: "Norman.Kern" <norman.kern@gmx.com>, ceph-devel@vger.kernel.org
Subject: Re: Ceph Kernel client bad performance for 5.4
Date: Mon, 10 May 2021 09:30:06 -0400	[thread overview]
Message-ID: <fbcb28d9bd8d50ef47750931904fabb78f28d182.camel@redhat.com> (raw)
In-Reply-To: <4badb69d-515f-ec30-5966-d26e145884bd@gmx.com>

On Sat, 2021-05-08 at 10:13 +0800, Norman.Kern wrote:
> Hi, guys,
> 
> 
> I'm using ceph nautilus in my production,  the kernel clients include 5.4 and 4.15, I found a problem in 5.4 sometimes: It's slower than fuse, but when I changed it
> to 4.15, it's recovered.
> for 5.4:
> root@WXRG0432:/mnt/test# rsync -ahHv --progress /root/test test-1
> sending incremental file list
> test
>          58.56M   5%    2.82MB/s    0:05:43  ^C
> for 4.15:
> root@WXRG0433:/mnt/test# rsync -ahHv --progress /root/test  test-2
> sending incremental file list
> test
>           1.05G 100%  316.25MB/s    0:00:03 (xfr#1, to-chk=0/1)
> 
> sent 1.05G bytes  received 35 bytes  299.67M bytes/sec
> Anyone have met the same problems with me?

v5.4 is quite old at this point. It would be good to also test something
newer if you're able. Something v5.12-ish would be ideal.

It's not clear what, exactly, you're testing here, but it looks like the
slowdown is in write activity. A slowdown of that magnitude sounds like
the client has stopped doing buffered I/O, but it's hard to say for
sure.

You may want to run both of these under strace, collecting syscall
timing and see if you can narrow down which syscalls are seeing the
biggest slowdowns. That may help us narrow down what's happening.

Thanks,
-- 
Jeff Layton <jlayton@redhat.com>


      reply	other threads:[~2021-05-10 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08  2:13 Ceph Kernel client bad performance for 5.4 Norman.Kern
2021-05-10 13:30 ` Jeff Layton [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=fbcb28d9bd8d50ef47750931904fabb78f28d182.camel@redhat.com \
    --to=jlayton@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=norman.kern@gmx.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;
as well as URLs for NNTP newsgroup(s).