[Bugs] [Bug 1495430] Make event-history feature configurable and have it disabled by default

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1495430



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/18395 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit 2a663389c5faf31f267be7f7fa98589019463c71
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date:   Thu Sep 7 18:48:34 2017 +0530

    mount/fuse: Make event-history feature configurable

    ... and disable it by default.

            Backport of:
            > Change-Id: Ia533788d309c78688a315dc8cd04d30fad9e9485
            > Reviewed-on: https://review.gluster.org/18242
            > BUG: 1467614
            > cherry-picked from commit
956d43d6e89d40ee683547003b876f1f456f03b6

    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: 1495430
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=vc33lEsoHE&a=cc_unsubscribe