linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: stan@hardwarefreak.com
Cc: "daobang wang" <wangdb1981@gmail.com>,
	"Mathias Burén" <mathias.buren@gmail.com>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID5 created by 8 disks works with xfs
Date: Sun, 01 Apr 2012 09:06:39 +0100	[thread overview]
Message-ID: <4F780C8F.8060105@anonymous.org.uk> (raw)
In-Reply-To: <4F77DF1F.6080103@hardwarefreak.com>

On 01/04/2012 05:52, Stan Hoeppner wrote:
[...]
>> 5. The real application is 200 D1(2Mb/s) video streams write 500MB
>> files on the XFS.
>
> This is a 50 MB/s raw stream rate with 200 writers to 200 target files.
>   It is very likely that neither 8 nor 16 disks in RAID5 will be able to
> sync this rate due to excessive head seeking, as I previously mentioned.

Handwaving slightly here, but I wonder whether using a lot of write 
cache will help aggregate writes here, since it's not actually random 
writes. If I were to model it as 250MB written every 5 seconds from 200 
writers, that might be able to be persuaded into 40 writes per second, 
which shouldn't cause excessive head seeking. It would be helpful if 
there were also enough additional cache that the reads for any RAID5 
read-modify-write cycles mostly came from cache and didn't need seeks. 
It should be possible to set this up such that, in the event of a crash 
or hardware failure, the filesystem and files are consistent, though 
obviously the last 5 seconds of each file is likely to be lost.

Having said that, even if it can be persuaded to work, I agree that it's 
still the wrong way to go; RAID10 or indeed RAID1+linear look like much 
better solutions.

Cheers,

John.


      reply	other threads:[~2012-04-01  8:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31  1:22 RAID5 created by 8 disks works with xfs daobang wang
2012-03-31  7:59 ` Mathias Burén
2012-03-31 20:09   ` Stan Hoeppner
2012-04-01  1:16     ` daobang wang
2012-04-01  2:05       ` daobang wang
2012-04-01  5:13         ` Stan Hoeppner
2012-04-01  3:51       ` Stan Hoeppner
2012-04-01  5:12         ` daobang wang
2012-04-01  5:40           ` Stan Hoeppner
2012-04-01  5:59             ` daobang wang
2012-04-01  6:20               ` daobang wang
2012-04-01  7:08                 ` Marcus Sorensen
2012-04-02  3:47                   ` Stan Hoeppner
2012-04-05  0:48                     ` daobang wang
     [not found]                       ` <CACwgYDOtCoVF-p+KKqPYxHhA4vWF78Ueecx9hcVWLoyxFWzV9Q@mail.gmail.com>
2012-04-05 21:01                         ` Stan Hoeppner
2012-04-06  0:25                           ` daobang wang
2012-04-06  2:33                             ` daobang wang
2012-04-06  6:00                               ` Jack Wang
2012-04-06  6:45                                 ` daobang wang
2012-04-06  6:49                                   ` daobang wang
2012-04-06  8:18                                     ` Stan Hoeppner
2012-04-06  8:45                                       ` daobang wang
2012-04-06 11:12                                         ` Stan Hoeppner
2012-04-18  2:23                                           ` daobang wang
2012-04-02  3:12                 ` Stan Hoeppner
2012-04-01 10:33             ` David Brown
2012-04-01 12:28               ` John Robinson
2012-04-02  6:59                 ` David Brown
     [not found]                 ` <CA+res+QkLi7sxZrD-XOcbR47CeJ5gADf7P6pa1w1oMf8CKSB4g@mail.gmail.com>
2012-04-02  8:01                   ` John Robinson
2012-04-02 10:01                     ` Jack Wang
2012-04-02 10:28                       ` John Robinson
2012-04-02 20:41                         ` Stan Hoeppner
2012-04-02  5:43               ` Stan Hoeppner
2012-04-02  7:04                 ` David Brown
2012-04-02 20:21                   ` Stan Hoeppner
2012-04-01  4:52       ` Stan Hoeppner
2012-04-01  8:06         ` John Robinson [this message]

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=4F780C8F.8060105@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.com \
    --cc=stan@hardwarefreak.com \
    --cc=wangdb1981@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;
as well as URLs for NNTP newsgroup(s).