On Thu, Aug 20, 2009 at 12:05 PM, Wei Dong wrote:
>
> I'm experiencing extremely slow auto-heal rate with glusterfs and I want to
> hear from you guys to see if it seems reasonable or something's wrong.
>
> I did a reconfiguration of the glusterfs running on our lab cluster.
> Originally we have 2
I also tested the read throughput under the same setting, only change
"stat path" to "cp path /dev/null". The aggregate throughput is also <
50 images/second. I'm also sure that the network is not saturated. We
are running some other web crawling task at the same time and the per
node read t
There's one thing obviously wrong in the previous email. GlusterFS is
able to use more than one CPU core because we are running 4x4 I/O
threads on each node. I got the 99% number from ganglia output which is
not correct.
Sorry for that
- Wei
Wei Dong wrote:
Hi All,
I'm experiencing extre
Hi All,
I'm experiencing extremely slow auto-heal rate with glusterfs and I want
to hear from you guys to see if it seems reasonable or something's wrong.
I did a reconfiguration of the glusterfs running on our lab cluster.
Originally we have 25 nodes, each provide 1 1.5T SATA disk, the data
