* RAID5 how chage chunck size from 64 to 128, 256 ? is it possible ?
@ 2008-02-09 4:43 Andreas-Sokov
2008-02-09 9:14 ` Justin Piszcz
0 siblings, 1 reply; 4+ messages in thread
From: Andreas-Sokov @ 2008-02-09 4:43 UTC (permalink / raw)
To: linux-raid
Hi linux-raid.
RAID5 how chage chunck size from 64 to 128, 256 ?
is it possible ?
Somebody did this ?
--
Best regards,
Andreas-Sokov
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RAID5 how chage chunck size from 64 to 128, 256 ? is it possible ?
2008-02-09 4:43 RAID5 how chage chunck size from 64 to 128, 256 ? is it possible ? Andreas-Sokov
@ 2008-02-09 9:14 ` Justin Piszcz
2008-02-09 22:31 ` Janek Kozicki
0 siblings, 1 reply; 4+ messages in thread
From: Justin Piszcz @ 2008-02-09 9:14 UTC (permalink / raw)
To: Andreas-Sokov; +Cc: linux-raid
When you reate the array its --chunk or -c -- I found 256 KiB to 1024 KiB
to be optimal.
Justin.
On Sat, 9 Feb 2008, Andreas-Sokov wrote:
> Hi linux-raid.
>
> RAID5 how chage chunck size from 64 to 128, 256 ?
> is it possible ?
> Somebody did this ?
>
> --
> Best regards,
> Andreas-Sokov
>
> -
> 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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RAID5 how chage chunck size from 64 to 128, 256 ? is it possible ?
2008-02-09 9:14 ` Justin Piszcz
@ 2008-02-09 22:31 ` Janek Kozicki
2008-02-10 9:03 ` Justin Piszcz
0 siblings, 1 reply; 4+ messages in thread
From: Janek Kozicki @ 2008-02-09 22:31 UTC (permalink / raw)
Cc: linux-raid
Justin Piszcz said: (by the date of Sat, 9 Feb 2008 04:14:51 -0500 (EST))
> When you reate the array its --chunk or -c -- I found 256 KiB to 1024 KiB
> to be optimal.
Hello Justin,
what is your typical bonnie++ invocation, to test your configuration?
Which fields are meaningful for you from this benchmark?
Do you use anything else for benchmarks?
eg: 'zcav /dev/sda > result' ?
I'm asking becuase I want to make some local benchmarks to determine
best chunk size in my HDD setup.
thanks in advance
--
Janek Kozicki |
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RAID5 how chage chunck size from 64 to 128, 256 ? is it possible ?
2008-02-09 22:31 ` Janek Kozicki
@ 2008-02-10 9:03 ` Justin Piszcz
0 siblings, 0 replies; 4+ messages in thread
From: Justin Piszcz @ 2008-02-10 9:03 UTC (permalink / raw)
To: Janek Kozicki; +Cc: linux-raid
On Sat, 9 Feb 2008, Janek Kozicki wrote:
> Justin Piszcz said: (by the date of Sat, 9 Feb 2008 04:14:51 -0500 (EST))
>
>> When you reate the array its --chunk or -c -- I found 256 KiB to 1024 KiB
>> to be optimal.
>
> Hello Justin,
>
> what is your typical bonnie++ invocation, to test your configuration?
> Which fields are meaningful for you from this benchmark?
>
> Do you use anything else for benchmarks?
> eg: 'zcav /dev/sda > result' ?
>
>
> I'm asking becuase I want to make some local benchmarks to determine
> best chunk size in my HDD setup.
>
> thanks in advance
> --
> Janek Kozicki |
> -
> 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
>
I use the following (3-iterations & average them):
/usr/bin/time /usr/sbin/bonnie++ -d /x/test -s 16384 -m p34 -n
16:100000:16:64 > $HOME/test"$i".txt 2>&1
I also use realistic testing as well such as untarring large files (>
1GiB) etc..
Justin.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-02-10 9:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-09 4:43 RAID5 how chage chunck size from 64 to 128, 256 ? is it possible ? Andreas-Sokov
2008-02-09 9:14 ` Justin Piszcz
2008-02-09 22:31 ` Janek Kozicki
2008-02-10 9:03 ` Justin Piszcz
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.