+++ This bug was initially created as a clone of Bug #1708180 +++ Description of problem: In one of the performance testing effort, we found that below options help improve the overall performance numbers of gluster-block workload: performance.io-thread-count 16 -> 32 performance.high-prio-threads 16 -> 32 performance.normal-prio-threads 16 -> 32 performance.low-prio-threads 16 -> 32 performance.least-prio-threads 1 -> 4 client.event-threads 2 -> 8 server.event-threads 1 -> 8 performance.client-io-threads off -> on I was thinking its good idea to add this changes to current block profile, as we have data showing improvements in perf results. Also, its good idea to re-validate the existing gluster-block profile options in /var/lib/glusterd/groups/gluster-block --- Additional comment from Prasanna Kumar Kalever on 2019-05-09 15:40:44 IST --- @Elko Kuric do you have graphs showing improvements with these changes ? Thanks!
@Saravana, the RHGS build is available and this issue is fixed on glusterfs-6.0-9. Can we create rhgs-server-container with the same fix?
Prasanna, we can not move this bugzilla to ON_QA unless we have the fix available in container. Bringing it back to POST.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3257