All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Marcus <CMarcus@Media-Brokers.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] RAID chunk size & LVM 'offset' affecting RAID stripe alignment
Date: Mon, 28 Jun 2010 14:56:16 -0400	[thread overview]
Message-ID: <4C28F050.9090703@Media-Brokers.com> (raw)
In-Reply-To: <4C246A7A.50202@tlinx.org>

On 2010-06-25 4:36 AM, Linda A. Walsh wrote:
> Doug Ledford wrote:
>> Correction: all reads benefit from larger chunks now a days.  The only
>> reason to use smaller chunks in the past was to try and get all of
>> your drives streaming data to you simultaneously, which effectively
>> made the total aggregate throughput of those reads equal to the
>> throughput of one data disk times the number of data disks in the
>> array.  With modern drives able to put out 100MB/s sustained by
>> themselves, we don't really need to do this any more, ....

> I would regard 100MB/s as moderately slow.  For files in my
> server cache, my Win7 machine reads @ 110MB/s over the network,

My understanding is Gigabit ethernet is only capable of topping out at
about 30MB/s, so, I'm curious what kind of network you have? 10GBe? Fiber?

-- 

Best regards,

Charles

  parent reply	other threads:[~2010-06-28 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 21:24 [linux-lvm] Volume alignment over RAID Linda A. Walsh
2010-05-21  5:10 ` Luca Berra
2010-05-21  6:48   ` Linda A. Walsh
2010-05-21  7:19     ` Lyn Rees
2010-05-21 18:50       ` Linda A. Walsh
2010-05-22  7:36         ` Luca Berra
2010-05-22  7:23     ` Luca Berra
2010-05-27 16:40       ` Doug Ledford
2010-06-21  4:26         ` [linux-lvm] RAID chunk size & LVM 'offset' affecting RAID stripe alignment Linda A. Walsh
2010-06-23 18:59           ` Doug Ledford
2010-06-25  8:36             ` Linda A. Walsh
2010-06-26  1:50               ` Doug Ledford
2010-06-28 18:56               ` Charles Marcus [this message]
2010-06-29 21:33                 ` Linda A. Walsh

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=4C28F050.9090703@Media-Brokers.com \
    --to=cmarcus@media-brokers.com \
    --cc=linux-lvm@redhat.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.