On Sun, Sep 12, 2010 at 3:20 AM, Henrique Haas <henrique at dz6web.com> wrote: > Hello Jacob, > > Greater block sizes gave me much much better results, about *58MB/s* on a > 1GigE !!!! > So.. my concern now is about smaller files be shared using Gluster. > Any tunning tips for these kind of files (I'm using Ext4 and Gluster 3.0.2)? "dd" won't give you accurate results for testing file copies. Your slow writes with small block sizes are more likely to high I/O and read starve on the client side than the server/write side. You should test something more real world instead. For instance: for i in `seq 1 1000000` ; do dd if=/dev/urandom of=$i bs=1K count=1 ; done That will create 1,000,000 1KB files (1GB of information) with random data on your local hard disk in the current directory. Most file systems store 4K blocks, so actual disk usage will be 4GB. Now copy/rsync/whatever these files to your Gluster storage. (use a command like "time cp /blah/* /mnt/gluster/" to wallclock it). Now tar up all the files, and do the copy again using the single large tar file. Compare your results.
