From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Tux mailing list <tux-list@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Lots of questions about tux and kernel setup
Date: Mon, 5 Nov 2001 15:00:11 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.30.0111051429040.18879-100000@mustard.heime.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111051519560.3082-100000@ahriman.bucharest.roedu.net>
> to answer other "not asked" questions of yours ill point you to :
> http://www.specbench.org/osg/web99/results/res2000q4/web99-20001127-00075.html
>
> as that should help you very much :) (that /proc tweaking its pretty cool)
Thanks!
Just one thing...
I need redundancy, so I can't go with RAID 0. I thought I'd go with RAID
4, to avoid reading the parity info (and thereby wasting time), and still
have some quite good redundancy.
Q: Should I use hardware RAID or software RAID here? I can see they've
been using a rather large stripe (or chunk) size on the RAID (2MB). The
RAID controller I planned to use only supports up to 512kB stripes. As I
said, the files I'm reading are rather large - up to 10GB each, or at
least 1GB. I'm reading 4-7Mbps (500-900kB) per connection and each
connection reads only one file. Will a large stripe size help me here?
roy
---
Computers are like air conditioners.
They stop working when you open Windows.
next prev parent reply other threads:[~2001-11-05 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 12:33 Lots of questions about tux and kernel setup Roy Sigurd Karlsbakk
2001-11-05 13:26 ` Mihai RUSU
2001-11-05 14:00 ` Roy Sigurd Karlsbakk [this message]
2001-11-05 14:11 ` Mihai RUSU
2001-11-05 14:50 ` Michael E Brown
2001-11-05 15:42 ` Roy Sigurd Karlsbakk
[not found] <Pine.LNX.4.10.10111051119360.13543-100000@coffee.psychology.mcmaster.ca>
2001-11-05 16:47 ` Roy Sigurd Karlsbakk
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=Pine.LNX.4.30.0111051429040.18879-100000@mustard.heime.net \
--to=roy@karlsbakk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tux-list@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 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).