# Would there be any CPU gains by disabling xpack-security and xpack.transport.ssl in Elasticsearch 7.17

**URL:** https://discuss.elastic.co/t/would-there-be-any-cpu-gains-by-disabling-xpack-security-and-xpack-transport-ssl-in-elasticsearch-7-17/344878
**Category:** Elasticsearch
**Created:** [October 12, 2023, 7:29am UTC](https://discuss.elastic.co/t/would-there-be-any-cpu-gains-by-disabling-xpack-security-and-xpack-transport-ssl-in-elasticsearch-7-17/344878 "2023-10-12T07:29:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Muthukumaran\_Kothand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muthukumaran_kothand/32/46017_2.png) [@Muthukumaran\_Kothand](https://discuss.elastic.co/u/Muthukumaran_Kothand)
#### Post date: [October 12, 2023, 7:29am UTC](https://discuss.elastic.co/t/would-there-be-any-cpu-gains-by-disabling-xpack-security-and-xpack-transport-ssl-in-elasticsearch-7-17/344878/1 "2023-10-12T07:29:40Z")

</div>

Hi,

We run our ES Cluster in a completely closed on-prem Kubernetes environment wherein we do not expose ES ports for any external access (hence no security-hazard)

In this case, I wanted to understand if disabling `xpack.security` as well as `xpack.transport.ssl` would yield any CPU-usage gains ? On many instances, I have observed the SSL-handling code-path appears in `hot_threads` output with higher CPU-usage.

Regards  
Muthu

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 9, 2023, 7:29am UTC](https://discuss.elastic.co/t/would-there-be-any-cpu-gains-by-disabling-xpack-security-and-xpack-transport-ssl-in-elasticsearch-7-17/344878/2 "2023-11-09T07:29:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.