ef61a79f33
For gluster-block workloads I/O is always with o-direct so it doesn't benefit by any of the perf xlators so disabling all of them to save on memory. performance.quick-read=off performance.read-ahead=off performance.io-cache=off performance.stat-prefetch=off performance.write-behind=off performance.open-behind=off performance.readdir-ahead=off We want the I/O on the file to be with o-direct network.remote-dio=enable Options that are proven to give good performance with VM workloads which is very similar to gluster-block cluster.eager-lock=enable cluster.quorum-type=auto cluster.data-self-heal-algorithm=full cluster.locking-scheme=granular cluster.shd-max-threads=8 cluster.shd-wait-qlength=10000 features.shard=on It is better to turn off things we are not using user.cifs=off It is better to have allow-insecure to be on so that ports that are > 1024 in tcmu-runner are allowed. server.allow-insecure=on Change-Id: I9a21c824fa42242f02b57569feedd03d9b6f9439 BUG: 1450010 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: https://review.gluster.org/17254 Smoke: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Niels de Vos <ndevos@redhat.com> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Jeff Darcy <jeff@pl.atyp.us> |
||
---|---|---|
.github | ||
api | ||
build-aux | ||
cli | ||
contrib | ||
doc | ||
events | ||
extras | ||
geo-replication | ||
glusterfsd | ||
heal | ||
libglusterfs | ||
rpc | ||
tests | ||
tools | ||
xlators | ||
.gitignore | ||
.mailmap | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
configure.ac | ||
CONTRIBUTING | ||
COPYING-GPLV2 | ||
COPYING-LGPLV3 | ||
glusterfs-api.pc.in | ||
glusterfs.spec.in | ||
INSTALL | ||
libgfchangelog.pc.in | ||
libgfdb.pc.in | ||
MAINTAINERS | ||
Makefile.am | ||
NEWS | ||
README.md | ||
rfc.sh | ||
run-tests-in-vagrant.sh | ||
run-tests.sh | ||
site.h.in | ||
THANKS |
For information about contributing to GlusterFS, please follow Contributing to GlusterFS community.
GlusterFS does not follow the GitHub: Fork & pull workflow but use Gerrit for code review.
The development guidelines are detailed in Development Workflow.
The GlusterFS documentation can be found at our Read the Docs site.
For more info, please visit gluster.org.