| /var/lib/glusterd/groups/virt is a good start for ideas, notably some thread settings and choose-local=off to improve read performance. If you don’t have at least 10 cores on your servers, you may want to lower the recommended shd-max-threads=8 to no more than half your CPU cores to keep healing from swamping out regular work. It’s also starting to depend on what your backing store and networking setup are, so you’re going to want to test changes and find what works best for your setup. In addition to the virt group settings, I use these on most of my volumes, SSD or HDD backed, with the default 64M shard size: performance.io-thread-count: 32 # seemed good for my system, particularly a ZFS backed volume with lots of spindles client.event-threads: 8 cluster.data-self-heal-algorithm: full # 10G networking, uses more net/less cpu to heal. probably don’t use this for 1G networking? performance.stat-prefetch: on cluster.read-hash-mode: 3 # distribute reads to least loaded server (by read queue depth) and these two only on my HDD backed volume: performance.cache-size: 1G performance.write-behind-window-size: 64MB but I suspect these two need another round or six of tuning to tell if they are making a difference. I use the throughput-performance tuned profile on my servers, so you should be in good shape there.
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
