Renchu,
I didn't see anything about average file size and read/write mix. One example
of how to observe both of these, as well as latency and throughput - on server
run these commands:
# gluster volume profile your-volume start
# gluster volume profile your-volume info /tmp/dontcare
# sleep
Dear Ben,
Very interesting answer from yours of how to find out where the bottleneck is.
These commands and paramters (iostat, sar) should maybe be documented on the
Gluster wiki.
I have a question for you, in order to better use my CPU cores (6 cores per
node) I was wondering if I should
On 22 Feb 2015, at 20:47, ML mail mlnos...@yahoo.com wrote:
Dear Ben,
Very interesting answer from yours of how to find out where the bottleneck
is. These commands and paramters (iostat, sar) should maybe be documented on
the Gluster wiki.
Good idea. Any interest in creating a wiki
