All of lore.kernel.org
 help / color / mirror / Atom feed
From: juncheng bai <baijuncheng@unitedstack.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-fsdevel@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Performance degrad on big cluster
Date: Fri, 24 Jul 2015 22:58:56 +0800	[thread overview]
Message-ID: <55B252B0.7010301@unitedstack.com> (raw)
In-Reply-To: <CAM9_UU_sKYrnvTeScZYh3Wi-X12zGZYXXevkW_Y-78f7rd2TpA@mail.gmail.com>

Hi all,
    We meet a performance degrad in one of our cluster. Our
randwrite latency degraded from 1ms to 5ms(fio -ioengine=rbd
iodepth=1)
    The cluster has about 200 osds runing on Intel 3500 SSD, we run
both qemu and ceph-osd on the hosts. The network for ceph is 10GbE.
    While the cluster is smaller and not so many qemu processes,
the IO latency is about 1ms, but now the latency is 5ms.
    I use strace to  get the time for syscall, all syscall (writev,
io_sub mit, recvfrom,sendmsg,lseek,fgetxattr etc.)  use 300us to 600us.
The syscall time on a small and idle cluster is near to 0us.
    After checked serval clusters, I come to a conclusion:
    num_of_osds     num_of_threads_on_host    time_of_syscall(us)
    200                       10000             300-600
    100                       5000              200-500
    70                        2500              100-300
    9                         750               20-60

   The threads on one of 200 osds cluster's host is like this:
   name num_of_processes  num_of_threads  num_of_threads_per_process
   qemu-kvm    49                9748            198
   ceph-osd    6                 5707            951

   I think too many threads on the host lead to high latency of ceph-osd 
process, and cause to high I/O latency from the client-side.

   Anyone's help is welcome.

Thanks!

      reply	other threads:[~2015-07-24 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 17:49 Performance degrad on big cluster Ketor D
2015-07-24 14:58 ` juncheng bai [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=55B252B0.7010301@unitedstack.com \
    --to=baijuncheng@unitedstack.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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.