From: "JaniD++" <djani22@dynamicweb.hu>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 performance question
Date: Sun, 27 Nov 2005 17:21:17 +0100 [thread overview]
Message-ID: <001f01c5f36e$9ec7e620$0400a8c0@dcccs> (raw)
In-Reply-To: 200511271839.16480.a1426z@gawab.com
Hi,
----- Original Message -----
From: "Al Boldi" <a1426z@gawab.com>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-raid@vger.kernel.org>; "Neil Brown" <neilb@suse.de>
Sent: Sunday, November 27, 2005 4:39 PM
Subject: Re: RAID0 performance question
> Neil Brown wrote:
> > On Saturday November 26, djani22@dynamicweb.hu wrote:
> > >
> > > The cat /dev/nb# >/dev/null makes ~ 350 Mbit/s on each nodes.
>
> Why is this so slow?
Yes. :-)
This system tries to serv about 500-800 downloads.
The final goal is the 1k! ;-)
And this point why i am asking the list, because the HW performance is much
more without raid0 layer. :-/
The 780-800 Mbit is "almost" enough to 1k downloaders.
> Or is this the max node-HD throughput?
Yes.
> What's the node HW config?
P4-3G -HT
12x 200Gb hdd (10 IDE+2 SATA)
2G Ram
realtek gige.
RAID5 inside! ;-)
>
> > > The cat /dev/nb0 + nb1 + nb2 + nb3 in one time parallel makes ~
780-800
> > > Mbit/s. - i think this is my network bottleneck.
>
> How much do you get w/ nb0+1,2,3 and nb0+1+2,3 respectively?
I unable to test write, because this is a productive system.
Think this value is about 75-80 per node and ~200-250 in md31.
>
> > > But the cat /dev/md31 >/dev/null (RAID0, the sum of 4 nodes) only
makes
> > > ~450-490 Mbit/s, and i dont know why....
> > >
> > > Somebody have an idea? :-)
> >
> > Try increasing the read-ahead setting on /dev/md31 using 'blockdev'.
> > network block devices are likely to have latency issues and would
> > benefit from large read-ahead.
>
> Also try larger chunk-size ~4mb.
Ahh.
This is what i can't do. :-(
I dont know how to backup 8TB! ;-)
Thanks,
Janos
>
> --
> Al
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-11-27 16:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 19:34 mdadm 2.1: command line option parsing bug? Andreas Haumer
2005-11-21 23:21 ` Neil Brown
2005-11-22 11:21 ` Michael Tokarev
2005-11-24 5:15 ` Neil Brown
2005-11-22 15:41 ` Molle Bestefich
2005-11-24 5:25 ` Neil Brown
2005-11-24 7:31 ` Ross Vandegrift
2005-12-15 1:53 ` Molle Bestefich
2005-12-15 4:19 ` Neil Brown
2005-12-15 10:37 ` Molle Bestefich
2005-11-22 22:05 ` Andre Noll
2005-11-26 14:04 ` RAID0 performance question JaniD++
2005-11-26 15:56 ` Raz Ben-Jehuda(caro)
2005-11-26 16:08 ` JaniD++
2005-11-26 17:11 ` Lajber Zoltan
2005-11-26 17:34 ` JaniD++
2005-11-26 19:47 ` Lajber Zoltan
2005-11-26 23:27 ` Neil Brown
2005-11-26 23:37 ` JaniD++
2005-11-27 15:39 ` Al Boldi
2005-11-27 16:21 ` JaniD++ [this message]
2005-11-27 17:40 ` Al Boldi
2005-11-27 19:02 ` JaniD++
2005-11-30 23:13 ` JaniD++
2005-12-02 19:53 ` Al Boldi
2005-12-18 0:13 ` JaniD++
2005-12-19 11:16 ` Al Boldi
2005-11-22 1:14 ` JaniD++
2005-11-23 10:48 ` JaniD++
2005-12-21 1:40 ` Neil Brown
2005-11-22 1:56 ` JaniD++
2005-12-22 4:49 ` Neil Brown
2005-11-23 9:44 ` JaniD++
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='001f01c5f36e$9ec7e620$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=a1426z@gawab.com \
--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 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.