# Identify indexing performance bottleneck

**URL:** https://discuss.elastic.co/t/identify-indexing-performance-bottleneck/252456
**Category:** Kibana
**Created:** [October 18, 2020, 4:47pm UTC](https://discuss.elastic.co/t/identify-indexing-performance-bottleneck/252456 "2020-10-18T16:47:58Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [October 20, 2020, 1:05am UTC](https://discuss.elastic.co/t/identify-indexing-performance-bottleneck/252456/4 "2020-10-20T01:05:48Z")

</div>

Related post maybe [CPU at 100% with XPACK security Enabled - ES 7.3](https://discuss.elastic.co/t/cpu-at-100-with-xpack-security-enabled-es-7-3/214544)

How may indices, shards, replicas? Are you using enhanced access, field or document level checks?

---

_[View the full topic](https://discuss.elastic.co/t/identify-indexing-performance-bottleneck/252456)._