All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Łukasz Oleś" <lukasz.oles@open-e.com>
To: Chris Weiss <cweiss@gmail.com>
Cc: scst-devel@lists.sourceforge.net, linux-raid@vger.kernel.org
Subject: Re: [Scst-devel] Tuning scst windows and sw raid5
Date: Fri, 22 Apr 2011 16:35:37 +0200	[thread overview]
Message-ID: <201104221635.38092.lukasz.oles@open-e.com> (raw)
In-Reply-To: <BANLkTiktSichu5PT7LUb0nLzOe=chq3s1A@mail.gmail.com>

On Friday 22 of April 2011 16:19:48 you wrote:
> On Fri, Apr 22, 2011 at 9:08 AM, Łukasz Oleś <lukasz.oles@open-e.com> wrote:
> > Hi,
> > 
> > I'm trying to tune Software Raid5, SCST and Windows Initiator to get best
> > read/write performance.
> 
> My first recommendation is to stick with blockio due to the raid5
> write hole possibility when using software raid.
> 
> what windows version, and if not server2008, did you align the
> partitions? (there's a 2003 and a 2008 R2)
2008 R2

> dd is going to use the initiator OS's cache, make sure your test file
> size is 2x the ram in the initiator, if not the target too.
On initiator I have 2GB RAM and I'm copying 20GB file.

> Also xfs is much better at dealing with large files than ntfs.  Best
> apple to apples test is going to be on raw unformated partitions
What this test(testing on raw partitions) can tell me? In the end I have to 
use filesystem.

> I'm not familiar with BST5.  I typically use iometer for both OS's.
I will try it.

--
Lukasz Oles

--
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

  reply	other threads:[~2011-04-22 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201104221608.50195.lukasz.oles@open-e.com>
2011-04-22 14:19 ` [Scst-devel] Tuning scst windows and sw raid5 Chris Weiss
2011-04-22 14:35   ` Łukasz Oleś [this message]
2011-04-22 14:48     ` Chris Weiss

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=201104221635.38092.lukasz.oles@open-e.com \
    --to=lukasz.oles@open-e.com \
    --cc=cweiss@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    /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.