[mailto:anand.av...@gmail.com]
Verzonden: 03 December 2010 14:03
Aan: Gotwalt, P.
CC: gluster-users@gluster.org
Onderwerp: Re: [Gluster-users] performance stops at 1Gb
Do both read and write throughput peak at 1Gbit/s? What is the block size
used for performing I/O? Can you get the output of -
1. dd if
Do both read and write throughput peak at 1Gbit/s? What is the block size
used for performing I/O? Can you get the output of -
1. dd if=/dev/zero of=/mnt/stripe/file bs=1M count=1K
2. dd if=/mnt/stripe/file of=/dev/null bs=1M count=1K
Just one instance of dd is enough as the client network inter
Craig,
Using multiple parallel bonnie++ benchmarks (4,8,16) does use several
files. These file are 1GB each, and we take care there will be at least
32 of them. As we have multiple processes (4,8,16 bonnie++s) and each
uses several files, we spread the io over different storage bricks. I
can see t
Peter -
Using Gluster the performance of any single file is going to be
limited to the performance of the server on which it exists, or in the
case of a striped volume of the server on which the segment of the file
you are accessing exists. If you were able to start 4 processes,
accessing d
Hi All,
I am doing some tests with gluster (3.1) and have a problem of not
getting higher throughput than 1 Gb (yes bit!) with 4 storage bricks.
My setup:
4 storage bricks (dualcore, 4GB mem) each with 3 sata 1Tb disks,
connected to a switch with 1 Gb nics. In my tests I only use 1 SATA
disk as
