On Wed, Jan 14, 2009 at 6:56 PM, Brent A Nelson <brent@xxxxxxxxxxxx> wrote:
Yes. But with 2.0, Non-blocking I/O is introduced. Hence the client thread will not be blocked on I/O operations.
regards,
On Wed, 14 Jan 2009, Vikas Gorur wrote:I found io-threads on the client to be a major gain. When the client is very busy with io tasks, io-threads seems to eliminate latency in metadata operations (e.g., ls doesn't hang for ages). It made the client feel much more responsive.
As for io-threads above/below unify, there is not much to be gained by
using io-threads on the client side, since there are no slow
operations on the client side (just a straight code path from the
application to the server). Using it on the server makes sense because
it lets GlusterFS do other useful work while one thread is waiting for
a read/write from/to the underlying filesystem finishes.
Yes. But with 2.0, Non-blocking I/O is introduced. Hence the client thread will not be blocked on I/O operations.
regards,
Thanks,
Brent
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
Raghavendra G
