public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: File system testing
Date: Thu, 18 Sep 2014 10:04:07 +0200	[thread overview]
Message-ID: <3311713.JX0yBPqh8Z@andromeda> (raw)
In-Reply-To: <5419ED08.2020408@alectenharmsel.com>

[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]


On Wednesday, September 17, 2014 04:20:24 PM Alec Ten Harmsel wrote:
> As far as HDFS goes, I would only set that up if you will use it for
> Hadoop or related tools. It's highly specific, and the performance is
> not good unless you're doing a massively parallel read (what it was
> designed for). I can elaborate why if anyone is actually interested.
> 
> We use Lustre for our high performance general storage. I don't have 
any
> numbers, but I'm pretty sure it is *really* fast (10Gbit/s over IB
> sounds familiar, but don't quote me on that).

I think any shared filesystem will be fast if you have a lot of bandwidth :)
When comparing network filesystems it makes sense to keep the hardware 
identical reduce the overhead to a percentage. Eg. What is the theoretical 
maximum speed for the used network. (10Gbit/s) and what is the actual 
maximum speed you get with:
1) a single really large file (200GB)
2) a lot (100,000) smaller files (2MB)

Then you can make an estimate on what to expect when using a 1Gbit/s 
network. I somehow don't expect James to have InfiniBand available for his 
research?
Personally, when choosing between InfiniBand and Ethernet, I'm tempted 
to go with dedicated bonded 10Gbit/s links because of the price-
difference. (A quick research shows me that Infiniband is about 3x as 
expensive for the same throughput)

> > Personally, I would read up on these and see how they work. Then,
> > based on that, decide if they are likely to assist in the specific
> > situation you are interested in.
> 
> Always good advice.

It saves time to do some simple research (the reading type) before 
actually doing tests.

--
Joost

[-- Attachment #2: Type: text/html, Size: 6197 bytes --]

  parent reply	other threads:[~2014-09-18  8:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 19:07 [gentoo-user] File system testing James
2014-09-17  7:45 ` J. Roeleveld
2014-09-17 15:55   ` [gentoo-user] " James
2014-09-17 19:34     ` J. Roeleveld
2014-09-17 20:20       ` Alec Ten Harmsel
2014-09-17 20:56         ` James
2014-09-18  8:24           ` J. Roeleveld
2014-09-18  9:48             ` Rich Freeman
2014-09-18 10:22               ` J. Roeleveld
2014-09-19 13:41             ` James
2014-09-19 14:56               ` Rich Freeman
2014-09-19 15:06                 ` J. Roeleveld
2014-09-19 15:02               ` J. Roeleveld
2014-09-18  8:04         ` J. Roeleveld [this message]
2014-09-18  9:17         ` Kerin Millar
2014-09-18 13:12           ` Alec Ten Harmsel
2014-09-19 15:21             ` Kerin Millar
2014-09-17 18:10 ` [gentoo-user] " Hervé Guillemet
2014-09-17 18:21   ` J. Roeleveld
2014-09-17 21:05     ` [gentoo-user] " James
2014-09-18  7:29       ` J. Roeleveld
2014-09-18  8:28     ` [gentoo-user] " Kerin Millar
2014-09-25 20:56     ` thegeezer
2014-09-18 15:32   ` [gentoo-user] " James
2014-09-25 20:47 ` [gentoo-user] " thegeezer

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=3311713.JX0yBPqh8Z@andromeda \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.gentoo.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