CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Greg Farnum <greg@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: how to debug slow rbd block device
Date: Tue, 22 May 2012 21:40:56 +0200	[thread overview]
Message-ID: <4FBBEBC8.1000205@profihost.ag> (raw)
In-Reply-To: <B141A2FBE87F4859AF931D71A339468E@inktank.com>

Am 22.05.2012 21:35, schrieb Greg Farnum:
> What does your test look like? With multiple large IOs in flight we can regularly fill up a 1GbE link on our test clusters. With smaller or fewer IOs in flight performance degrades accordingly.

iperf shows 950Mbit/s so this is OK (from KVM host to OSDs)

sorry:
dd if=/dev/zero of=test bs=4M count=1000; dd if=test of=/dev/null bs=4M 
count=1000;
1000+0 records in
1000+0 records out
4194304000 bytes (4,2 GB) copied, 99,7352 s, 42,1 MB/s

1000+0 records in
1000+0 records out
4194304000 bytes (4,2 GB) copied, 47,4493 s, 88,4 MB/s

Greets
Stefan

> On Tuesday, May 22, 2012 at 5:45 AM, Stefan Priebe - Profihost AG wrote:
>
>> Hi list,
>>
>> my ceph block testcluster is now running fine.
>>
>> Setup:
>> 4x ceph servers
>> - 3x mon with /mon on local os SATA disk
>> - 4x OSD with /journal on tmpfs and /srv on intel ssd
>>
>> all of them use 2x 1Gbit/s lacp trunk.
>>
>> 1x KVM Host system (2x 1Gbit/s lacp trunk)
>>
>> With one KVM i do not get more than 40MB/s and my network link is just
>> at 40% of 1Gbit/s.
>>
>> Is this expected? If not where can i start searching / debugging?
>>
>> Thanks,
>> Stefan
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org (mailto:majordomo@vger.kernel.org)
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>

  reply	other threads:[~2012-05-22 19:40 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 [this message]
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
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=4FBBEBC8.1000205@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox