CEPH filesystem development
 help / color / mirror / Atom feed
From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Stefan Majer <stefan.majer@gmail.com>
Cc: Hannes Reinecke <hare@suse.de>,
	Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	Mark Nelson <mark.nelson@inktank.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Infiniband 40GB
Date: Mon, 04 Jun 2012 11:21:56 +0200	[thread overview]
Message-ID: <4FCC7E34.7040005@univ-nantes.fr> (raw)
In-Reply-To: <CADdPHGvgE7ai6yjzsKmL9bfqEpyx+qxQaUKoOOYjiT4ZCJ-A0g@mail.gmail.com>

Le 04/06/2012 10:23, Stefan Majer a écrit :
> Hi Hannes,
>
> our production environment is running on 10GB infrastructure. We had a
> lot of troubles till we got to where we are today.
> We use Intel X520 D2 cards on our OSD´s and nexus switch
> infrastructure. All other cards we where testing failed horrible.
>

we have Intel Corporation 82599EB 10 Gigabit Dual Port Backplane 
Connection (rev 01)... Don't know the 'commercial name'. ixgbe driver.


> Some of the problems we encountered have been:
> - page allocation failures in the ixgbe driver --> fixed in upstream
> - problems with jumbo frames, we had to disable tso, gro, lro -- >
> this is the most obscure thing
> - various tuning via sysctl in the net.tcp and net.ipv4 area --> this
> was also the outcome of stefan´s benchmarking odysee.

some tuning we made :

-> Turning off Virtualisation extension in BIOS. Don't know why, but it 
gaves us crappy performance. We usually put it on, because we use KVM a 
lot. In our case, OSD are in bare metal and disabling virtualisation 
extension gives us a very big boost.
It may be a BIOS bug in our machines (DELL M610).

-> One of my colleague played with receive flow steeting ; the intel 
card supports multi queue, so it seems we can gain a little with it :

!/bin/sh

for x in $(seq 0 23); do echo FFFFFFFF > 
/sys/class/net/eth2/queues/rx-${x}/rps_cpus; done
echo 16384 > /proc/sys/net/core/rps_sock_flow_entries
for x in $(seq 0 23); do echo 16384 > 
/sys/class/net/eth2/queues/rx-${x}/rps_flow_cnt; done


>
> But after all this we a quite happy actully and are only limited by
> the speed of the drives (2TB SATA).
> The fsync is a fdatasync in fact which is available in newer glibc. If
> you dont use btrfs (we use xfs) you need to use a recent glibc with
> fdatasync support.

Does it may explain why we see loosy performance with xfs right now ? 
That the main reason we're stuck with btrfs for the moment.

we're using debian 'stable' : libc is
libc6                                   2.11.3-3
probably too old ?

Cheers,
-- 
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr


--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-06-04  9:22 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03  8:10 Infiniband 40GB Stefan Priebe
2012-06-03 12:56 ` Mark Nelson
2012-06-04  6:22   ` Hannes Reinecke
2012-06-04  7:26     ` Stefan Priebe - Profihost AG
2012-06-04  7:39       ` Hannes Reinecke
2012-06-04  7:53         ` Stefan Priebe - Profihost AG
2012-06-04  8:02           ` Hannes Reinecke
2012-06-04  8:23             ` Stefan Majer
2012-06-04  9:21               ` Yann Dupont [this message]
2012-06-04  9:35                 ` Alexandre DERUMIER
2012-06-04  9:53                   ` Yann Dupont
2012-06-04  9:47                 ` Amon Ott
2012-06-04  9:58                   ` Yann Dupont
2012-06-04 11:40                   ` Alexandre DERUMIER
2012-06-04 12:59                     ` Mark Nelson
2012-06-04 13:07                       ` Alexandre DERUMIER
2012-06-04 13:28                         ` Mark Nelson
2012-06-04 15:11                           ` Gregory Farnum
2012-06-04 15:34                             ` Mark Nelson
2012-06-06 16:05                       ` Alexandre DERUMIER
2012-06-06 16:43                         ` Mark Nelson
2012-06-04 15:42                   ` Stefan Priebe
2012-06-05  7:08                     ` Amon Ott
2012-06-05  7:46                       ` Stefan Priebe - Profihost AG
2012-06-06 10:48                   ` Stefan Priebe - Profihost AG
2012-06-06 10:57                     ` Amon Ott
2012-06-06 11:02                       ` Stefan Priebe - Profihost AG
2012-06-07 11:33                         ` Amon Ott
2012-06-07 12:44                           ` Stefan Priebe - Profihost AG
2012-06-05  8:54               ` Stefan Priebe - Profihost AG
2012-06-04 12:28     ` Mark Nelson
2012-06-04 12:34       ` Tomasz Paszkowski
2012-06-04 12:40         ` Mark Nelson
     [not found] <a81f3855-1c7d-447b-9bbf-6a891e372909@mailpro>
2012-06-07  3:31 ` Alexandre DERUMIER
2012-06-07 11:25   ` Alexandre DERUMIER
2012-06-07 17:15     ` Mark Nelson

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=4FCC7E34.7040005@univ-nantes.fr \
    --to=yann.dupont@univ-nantes.fr \
    --cc=ceph-devel@vger.kernel.org \
    --cc=hare@suse.de \
    --cc=mark.nelson@inktank.com \
    --cc=s.priebe@profihost.ag \
    --cc=stefan.majer@gmail.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