Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Jared Mauch <jared@puck.Nether.net>
To: Another Sillyname <anothersname@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: CPU requirements......
Date: Mon, 13 Jul 2015 12:26:01 -0400	[thread overview]
Message-ID: <20150713162600.GA16878@puck.nether.net> (raw)
In-Reply-To: <CAOS+5GGAL-8R7ZNd563Z-5oXbRw1QAswOKv7DstT5cLFdyR+Sw@mail.gmail.com>

On Mon, Jul 13, 2015 at 05:14:51PM +0100, Another Sillyname wrote:
> I've been testing a test RAID6 setup with a 5970 CPU that has worked fine.
> 
> As this box is almost exclusively going to be a file server I'm
> thinking of swapping to a G3258 processor, dual core, not overclocked
> and no hyperthreading or turbo features.
> 
> The box may also be used to do transcodes of media files from HD mpeg
> to x264 which is pretty CPU intensive......
> 
> Are there any likely issues with the RAID running on a substantially
> slower CPU?   I can't seem to find an recent/decent docs suggesting
> minimum CPU requirements for MDADM raid configs.

	you are likely to be I/O bound either on the drives
or on the controller card to the bus/cpu.

	While imperfect, take a look at doing
hdparm -t -T /dev/device-name

	This will give you an idea of what a userland process
will see as the performance for cached and non-cached reads.

	simply: the more you can keep in memory or on fast media
the better off you are.

	- Jared
-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.

  reply	other threads:[~2015-07-13 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 16:14 CPU requirements Another Sillyname
2015-07-13 16:26 ` Jared Mauch [this message]
2015-07-13 23:10 ` Adam Goryachev

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=20150713162600.GA16878@puck.nether.net \
    --to=jared@puck.nether.net \
    --cc=anothersname@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox