From: Bill Davidsen <davidsen@tmr.com>
To: Daniel Nilsson <daniel.n.nilsson@home.se>
Cc: Markus.Lidel@shadowconnect.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Performance degradation when using partitions
Date: Thu, 24 Nov 2005 13:41:52 -0500 [thread overview]
Message-ID: <43860970.3090804@tmr.com> (raw)
In-Reply-To: <20051124140825.GA15298@oden.homeip.net>
Daniel Nilsson wrote:
>On Tue, Nov 22, 2005 at 10:48:41AM -0500, Bill Davidsen wrote:
>
>
>>Daniel Nilsson wrote:
>>
>>
>>>While setting up a software RAID-5 array I started looking into the
>>>performance aspect of using partioned drives versus the whole disks
>>>for a RAID-5 array. I have an Adaptec 2400a controller which through
>>>the I2O kernel driver gives me access to 4x 250GB disks (JBOD mode).
>>>
>>>
>>Did you get an answer on this? And does it happen if you use the drives
>>directly, /dev/hdN or /dev/sdN instead of using I2O? I didn't see an
>>obvious speed penalty in raw access of drives vs. partitions, but I
>>lacked the hardware to really match your setup, particularly the I2O use
>>vs. direct access to /dev/sd[ef].
>>
>>
>
>Bill,
>
>No, I didn't get an answer on this. I've done some more experiments
>with the drives, but since they are connected to an Adaptec 2400A RAID
>controller (in JBOD mode) I need to go through some I2O driver in or
>to see the drives at all. So I never have direct access to these
>drives as /dev/hdN or /dev/sdN. There are however two different
>drivers available for this RAID controller, one is the standard I2O
>driver and the other one is the Adaptec dpt_i2o driver.
>
>The results are the same though whether I use the Linux I2O driver or
>the Adaptec dpt_i2o, the software raid array is rebuilding at roughly
>half the speed when the drives are partioned. I don't know what other
>data to provide in ordet to get any further in the testing.
>
>
Unfortunately, until someone else has the time and interest to make more
tests I don't see a good next step. I might be able to at least do some
better quantified tests later this weekend, but I have no I2O devices,
so it isn't going to tell much.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2005-11-24 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 18:23 Performance degradation when using partitions Daniel Nilsson
2005-11-22 15:48 ` Bill Davidsen
2005-11-24 14:08 ` Daniel Nilsson
2005-11-24 18:41 ` Bill Davidsen [this message]
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=43860970.3090804@tmr.com \
--to=davidsen@tmr.com \
--cc=Markus.Lidel@shadowconnect.com \
--cc=daniel.n.nilsson@home.se \
--cc=linux-kernel@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.