KV throughput regression in SSL scenarios

We have several  SSL scenarios. All of them indicate throughput regression between 6.5.0-2185 and 6.5.0-2201. I can't identify exact build/change because none of the builds in between work on CentOS.

Scenarios and results:

Max ops/sec, cbc-pillowfight, 2 nodes, 80/20 R/W, 512B JSON items, 1K batch size, TLS
http://showfast.sc.couchbase.com/#/timeline/Linux/kv/max_ops/all

This is basic pillowfight test with certification enabled ( --certpath root.pem )
6.5.0-2185 - 314K ops/sec 
6.5.0-2201 - 292K ops/sec
Logs: http://perf.jenkins.couchbase.com/job/ares/9352/console

Avg Throughput (ops/sec), Workload A, 3 nodes, 12 vCPU, SSL

http://showfast.sc.couchbase.com/#/timeline/Linux/kv/ycsb/all

YCSB WokloadA test with certification enabled when creating a connection object (Java SDK, builder.sslEnabled(true))

6.5.0-2185 - 2158K ops/sec
6.5.0-2201 - 172K ops/sec

6.5.0-2185 logs and CPU profiles: [http://perf.jenkins.couchbase.com/view/Weekly/job/hebe/2911/
]6.5.0-2201 logs and CPU profiles: http://perf.jenkins.couchbase.com/job/hebe/2909/console

Avg Throughput (queries/sec), Workload E, MOI, SSL, 4 nodes

http://showfast.sc.couchbase.com/#/timeline/Linux/n1ql/ycsb/MOI

Another YCSB test, workloadE

6.5.0-2158 - 10K ops/sec
6.5.0-2214 - 9K ops/sec