path: root/tests/bugs/fuse/bug-858215.t
diff options
authorKrutika Dhananjay <>2017-09-07 18:48:34 +0530
committerAmar Tumballi <>2017-09-24 06:22:07 +0000
commit956d43d6e89d40ee683547003b876f1f456f03b6 (patch)
tree55a2289be12d67edba0e6a3b4d9b7341ce46532a /tests/bugs/fuse/bug-858215.t
parentf449e53df7c07301b495b4ff688d165026dfd2d0 (diff)
mount/fuse: Make event-history feature configurable
... and disable it by default. This is because having it disabled seems to improve performance. This could be due to the lock contention by the different epoll threads on the circular buff lock in the fop cbks just before writing their response to /dev/fuse. Just to provide some data - wrt ovirt-gluster hyperconverged environment, I saw an increase in IOPs by 12K with event-history disabled for randrom read workload. Usage: mount -t glusterfs -o event-history=on $HOSTNAME:$VOLNAME $MOUNTPOINT OR glusterfs --event-history=on --volfile-server=$HOSTNAME --volfile-id=$VOLNAME $MOUNTPOINT Change-Id: Ia533788d309c78688a315dc8cd04d30fad9e9485 BUG: 1467614 Signed-off-by: Krutika Dhananjay <>
Diffstat (limited to 'tests/bugs/fuse/bug-858215.t')
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/bugs/fuse/bug-858215.t b/tests/bugs/fuse/bug-858215.t
index 389783be841..acfaca9bb4b 100755
--- a/tests/bugs/fuse/bug-858215.t
+++ b/tests/bugs/fuse/bug-858215.t
@@ -32,7 +32,7 @@ TEST $CLI volume start $V0;
EXPECT 'Started' volinfo_field $V0 'Status';
## Mount FUSE with caching disabled
-TEST glusterfs --entry-timeout=0 --attribute-timeout=0 -s $H0 --volfile-id $V0 $M0;
+TEST glusterfs --entry-timeout=0 --attribute-timeout=0 --event-history=on -s $H0 --volfile-id $V0 $M0;
## Test for checking whether the fops have been saved in the event-history
TEST ! stat $M0/newfile;