When we enable TLS/SSL on our data path we see a 50% performance hit in throughput.
Version-Release number of selected component (if applicable):
All glusterFS versions
Steps to Reproduce:
1. Run read / write perf test(say DD), note results
2. Enable TLS/SSL on the volume
3. Re run perf tests, compare throughput.
50% perf hit
Minimal performance hit.
After configuring AES128 cipher we have found performance is improved around 20% so we are using AES128 as a default cipher option.
REVIEW: https://review.gluster.org/23952 (socket: Use AES128 cipher in SSL if AES is supported by CPU) posted (#2) for review on master by MOHIT AGRAWAL
This bug is moved to https://github.com/gluster/glusterfs/issues/1050, and will be tracked there from now on. Visit GitHub issues URL for further details