# No improvement in query timings after improved mapping

**URL:** <https://discuss.elastic.co/t/no-improvement-in-query-timings-after-improved-mapping/176148>\
**Category:** Elasticsearch\
**Created:** [April 10, 2019, 6:52am UTC](https://discuss.elastic.co/t/no-improvement-in-query-timings-after-improved-mapping/176148 "2019-04-10T06:52:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Praneet\_Khandelwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/praneet_khandelwal/32/40565_2.png) [@Praneet\_Khandelwal](https://discuss.elastic.co/u/Praneet_Khandelwal)\
**Post date:** [April 10, 2019, 6:52am UTC](https://discuss.elastic.co/t/no-improvement-in-query-timings-after-improved-mapping/176148/1 "2019-04-10T06:52:56Z")

</div>

I currently have an index pattern in ES which has around 6k fields indexed (because the "dynamic" was set to true).  
As an enhancement, I created a new index pattern with around only 70 fields indexed in the mapping and reindexed data from older to newer indices.  
And for testing, I ran a bunch of same queries (taking into account that the new index has a reduced number of searchable fields) on both the indices and observed the timing in the 'took' variable. The observation is that the newer index performs similar or a bit worse than the older index.  
Can someone point out if I am doing something here or this behaviour might be possible in some cases (depending on other factors). Any help would be appreciated.

---

<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:** [May 8, 2019, 6:53am UTC](https://discuss.elastic.co/t/no-improvement-in-query-timings-after-improved-mapping/176148/2 "2019-05-08T06:53:05Z")

</div>

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