All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: Josh Durgin <josh.durgin@inktank.com>,
	Greg Farnum <greg@inktank.com>,
	ceph-devel@vger.kernel.org
Subject: Re: how to debug slow rbd block device
Date: Wed, 23 May 2012 10:15:34 +0200	[thread overview]
Message-ID: <4FBC9CA6.1030206@profihost.ag> (raw)
In-Reply-To: <CABYiri8LESPay495HX2s03nL0drOKqWgnXDQW3K71CQJ4MzuzQ@mail.gmail.com>

Am 23.05.2012 09:22, schrieb Andrey Korolyov:
> Hi,
> 
> For Stefan:
> 
> Increasing socket memory gave me about some percents on fio tests
> inside VM(I have measured
> 'max-iops-until-ceph-throws-message-about-delayed-write' parameter).
> What is more important, osd process, if possible, should be pinned to
> dedicated core or two, and all other processes should not use this
> core(you may do it via cg or manually), because even one four-core
> non-pinned VM process during test causes a drop of osd` throughput
> almost twice, same for any other heavy process on the host.
Tried that using taskset but i didn't get any noticable boost. Also the
kernel already prevents jumping from core 2 core whenever possible. As
these machines are dedicated to osd there is no other load.

> net.core.rmem_max = 16777216
> net.core.wmem_max = 16777216
> net.ipv4.tcp_rmem = 4096 87380 16777216
> net.ipv4.tcp_wmem = 4096 65536 16777216
This gaves me around 3-4 MB/s.

Stefan

  reply	other threads:[~2012-05-23  8:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 12:45 how to debug slow rbd block device Stefan Priebe - Profihost AG
2012-05-22 14:52 ` Andrey Korolyov
2012-05-22 19:27   ` Stefan Priebe
2012-05-22 19:35 ` Greg Farnum
2012-05-22 19:40   ` Stefan Priebe
2012-05-22 19:52     ` Greg Farnum
2012-05-22 20:13       ` Stefan Priebe
2012-05-22 20:30       ` Stefan Priebe
2012-05-22 20:48         ` Mark Nelson
2012-05-22 20:54           ` Stefan Priebe
2012-05-22 20:49         ` Greg Farnum
2012-05-22 21:00           ` Stefan Priebe
2012-05-22 21:11             ` Greg Farnum
2012-05-23  6:18               ` Stefan Priebe - Profihost AG
2012-05-23  6:30                 ` Josh Durgin
2012-05-23  7:01                   ` Stefan Priebe - Profihost AG
2012-05-23  7:19                     ` Josh Durgin
2012-05-23  7:22                       ` Stefan Priebe - Profihost AG
2012-05-23  7:33                         ` Josh Durgin
     [not found]                           ` <CABYiri8PXT9dpCGLE7dn=_PoW8CdLxqZF87OHe=dMXEWxogb_w@mail.gmail.com>
2012-05-23 19:54                             ` Josh Durgin
2012-05-23  8:20                       ` Stefan Priebe - Profihost AG
2012-05-23  8:29                         ` Josh Durgin
2012-05-23  7:22                   ` Andrey Korolyov
2012-05-23  8:15                     ` Stefan Priebe - Profihost AG [this message]
2012-05-23 11:47                     ` Mark Nelson
2012-05-23  8:30               ` Stefan Priebe - Profihost AG
2012-05-23  9:10                 ` Stefan Priebe - Profihost AG

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=4FBC9CA6.1030206@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=andrey@xdel.ru \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=josh.durgin@inktank.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 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.