linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mark delfman <markdelfman@googlemail.com>
To: Asdo <asdo@shiftmail.org>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: xfs > md 50% write performance drop on .30+ kernel?
Date: Tue, 13 Oct 2009 16:13:46 +0100	[thread overview]
Message-ID: <66781b10910130813u7f9ca010t7cd05214be729fff@mail.gmail.com> (raw)
In-Reply-To: <4AD48EFA.50303@shiftmail.org>

We dont use 10 ports, we use 8 ports > 36 port expander. The 8 ports
act as a single wide port.

We are hitting a performance limit of circa 1.6 - 1.9GBsec regardless
of number of drives, so it max's at around 8 / 9 drives (with 15K).
RAID6 around 900MBsec i recall.  We expect more with emerging
expanders.

We were hoping to use DM MPIO to increase performance using multiple
cards and paths, but MPIO at best matches performance of a single
card, most likely pulls it down.... but this is a different topic i
guess.

XFS in the past has often increased performance - not allows on simple
sequential writes, but FS's are a lot better at intelligently caching
data... so I am very keen to help in whatever way i can to resolve the
FS > MD performance problem.

Thanks again.... Mark


On Tue, Oct 13, 2009 at 3:30 PM, Asdo <asdo@shiftmail.org> wrote:
>
>> On Tue, Oct 13, 2009 at 2:12 PM, mark delfman
>> <markdelfman@googlemail.com> wrote:
>>
>>>
>>> We upgrading mainly because of support for the emerging LSI SAS2 cards
>>> (which we are beta testing now)
>>>
>
> What is this LSI SAS2 card you have with 10+ ports? The only 10+ ports LSI
> card I see is the 84016E and it is a SAS1.
>
> You say the driver for such card is included in the vanilla kernel at
> 2.6.30? That would be very nice... I grepped the 2.6.31 kernel source for
> LSI cards but I can't find device strings such as 84016E ...
>
> Thank you
>

  reply	other threads:[~2009-10-13 15:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 16:58 xfs > md 50% write performance drop on .30+ kernel? mark delfman
2009-10-12 18:40 ` Richard Scobie
2009-10-13  1:33 ` Christoph Hellwig
2009-10-13  1:57   ` NeilBrown
2009-10-13 11:06   ` mark delfman
2009-10-13 11:09     ` Majed B.
     [not found]       ` <66781b10910130412x309d9de2l574ba12a9ed4100a@mail.gmail.com>
2009-10-13 11:15         ` Majed B.
2009-10-13 11:29           ` mark delfman
2009-10-13 14:30           ` Asdo
2009-10-13 15:13             ` mark delfman [this message]
2009-10-13 15:15               ` mark delfman
2009-10-13 22:52     ` Christoph Hellwig
2009-10-14 19:34       ` mark delfman
2009-10-27 10:28         ` Thomas Fjellstrom
2009-10-27 11:11           ` Thomas Fjellstrom
2010-01-02  6:54             ` fibre raid
2009-10-13  3:38 ` Richard Scobie
2009-10-13 10:21   ` Asdo
2009-10-13 10:34     ` Mikael Abrahamsson
2009-10-13 14:49       ` Asdo
2009-10-13 19:53     ` Richard Scobie
2009-10-13 21:52       ` mark delfman
2009-10-13 18:49 ` Greg Freemyer

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=66781b10910130813u7f9ca010t7cd05214be729fff@mail.gmail.com \
    --to=markdelfman@googlemail.com \
    --cc=asdo@shiftmail.org \
    --cc=linux-raid@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 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).