# ElasticSearch 7.x index mapping update performance

**URL:** <https://discuss.elastic.co/t/elasticsearch-7-x-index-mapping-update-performance/360934>\
**Category:** Elasticsearch\
**Created:** [June 6, 2024, 8:03am UTC](https://discuss.elastic.co/t/elasticsearch-7-x-index-mapping-update-performance/360934 "2024-06-06T08:03:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakentop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jakentop/32/135081_2.png) [@Jakentop](https://discuss.elastic.co/u/Jakentop)\
**Post date:** [June 6, 2024, 8:03am UTC](https://discuss.elastic.co/t/elasticsearch-7-x-index-mapping-update-performance/360934/1 "2024-06-06T08:03:52Z")

</div>

We have about 2000w of data in a single index in a production environment, we are not currently deploying a cluster and only have a single slice. How long does it take to add a non-existing field using update mapping in this case, and will it block the business?  
I haven't found any implementation of the update mapping operation and its performance analysis at the moment. Can anyone help me?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 6, 2024, 8:22am UTC](https://discuss.elastic.co/t/elasticsearch-7-x-index-mapping-update-performance/360934/2 "2024-06-06T08:22:49Z")

</div>

Welcome!

It should take few milliseconds and will not block anything.