3de6ba0cd3
In some of the recent performance tests on gluster-as-vm-image-store use-case, it has been observed that sometimes the lone fuse thread can hit near-100% CPU utilization and become a performance bottleneck. Enabling client-io-threads (in addition to bumping up epoll threads on server and client side) has shown to be helpful in getting around this bottleneck and pushing more IOPs. Change-Id: I231db309de0e37c79cd44f5666da4cd776fefa04 fixes: bz#1630798 Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
19 lines
485 B
Plaintext
19 lines
485 B
Plaintext
performance.quick-read=off
|
|
performance.read-ahead=off
|
|
performance.io-cache=off
|
|
performance.low-prio-threads=32
|
|
network.remote-dio=enable
|
|
cluster.eager-lock=enable
|
|
cluster.quorum-type=auto
|
|
cluster.server-quorum-type=server
|
|
cluster.data-self-heal-algorithm=full
|
|
cluster.locking-scheme=granular
|
|
cluster.shd-max-threads=8
|
|
cluster.shd-wait-qlength=10000
|
|
features.shard=on
|
|
user.cifs=off
|
|
cluster.choose-local=off
|
|
client.event-threads=4
|
|
server.event-threads=4
|
|
performance.client-io-threads=on
|