Bug 1787325

Summary:	TLS/SSL access of GlusterFS mounts is slower than with no TLS/SSL enabled.
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	amukherj, bkunal, bturner, bugs, jstrunk, kramdoss, mchangir, moagrawa, mzink, rhinduja, rhs-bugs, rkothiya, sheggodu, storage-qa-internal, tmraz
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1612973	Environment:
Last Closed:	2020-03-12 14:28:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1612973
Bug Blocks:	1649191

Comment 1 Mohit Agrawal 2020-01-02 12:04:36 UTC

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

How reproducible:

Every time.

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.

Actual results:

50% perf hit

Expected results:

Minimal performance hit.

Comment 2 Mohit Agrawal 2020-01-02 12:05:56 UTC

After configuring AES128 cipher we have found performance is improved around 20% so we are using AES128 as a default cipher option.

Comment 3 Worker Ant 2020-01-02 12:09:12 UTC

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

Comment 4 Worker Ant 2020-03-12 14:28:03 UTC

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