[Bugs] [Bug 1495430] New: Make event-history feature configurable and have it disabled by default
bugzilla at redhat.com
bugzilla at redhat.com
Tue Sep 26 02:59:36 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1495430
Bug ID: 1495430
Summary: Make event-history feature configurable and have it
disabled by default
Product: GlusterFS
Version: 3.10
Component: core
Assignee: bugs at gluster.org
Reporter: kdhananj at redhat.com
CC: bugs at gluster.org
Description of problem:
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
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list