ZFS RAIDZ or RAID10？(附测试数据)
本帖最后由 pineweb 于 8-14-2012 20:06 编辑用ZFS上建了一个存储，测试了一下10快盘做RAID10和RAIDZ的数据，请大家看看，用作虚拟化ISCSI共享存储的话，选RAIDZ好还是RAID10好呢？
硬盘：10块SATA
内存：32G
CPU: 5620
测试结果见下图，图太长显示不清楚，请点击查看吧.
数据是用BONNIE++测的，附上说明
"Bonnie Results
Bonnie runs six tests, three that perform writes, and three that perform reads.
Here's the description provided by the benchmark's author for each of these tests:
Write Tests (Out)
* Per-Character: The file is written using the putc() stdio macro. The loop that does the writing should be small enough to fit into any reasonable I-cache.
The CPU overhead here is that required to do the stdio code plus the OS file space allocation.
* Block: The file is created using write(2). The CPU overhead should be just the OS file space allocation.
* Rewrite: Each Chunk (currently, the size is 16384) of the file is read with read(2), dirtied, and rewritten with write(2), requiring an lseek(2).
Since no space allocation is done, and the I/O is well-localized, this should test the effectiveness of the filesystem cache and the speed of data transfer.
Read Tests (In)
* Per-Character: The file is read using the getc() stdio macro. Once again, the inner loop is small. This should exercise only stdio and sequential input.
* Block: The file is read using read(2). This should be a very pure test of sequential input performance.
* Random Seeks: This test runs SeekProcCount (currently 4) processes in parallel, doing a total of 4000 lseek()s to locations in the file computed using
by random() in bsd systems, drand48() on sysV systems. In each case, the block is read with read(2). In 10% of cases, it is dirtied and written back with write(2).
The idea behind the SeekProcCount processes is to make sure there's always a seek queued up."
两个容量不一样 说句实话 参考性不高啊
页:
[1]