# Kibana search profiler accuracy

**URL:** <https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770>\
**Category:** Elasticsearch\
**Created:** [October 14, 2021, 7:15pm UTC](https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770 "2021-10-14T19:15:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [October 14, 2021, 7:15pm UTC](https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770/1 "2021-10-14T19:15:38Z")

</div>

I am debugging a long query and encountered below observation.  
The actual query takes 4.976 seconds.  
But the kibana search profiler states the search takes only 23.416 ms and aggregation takes 574.025 ms cumulatively each.  
I copy & pasted the payload so I'm sure the query strings are identical. And caching is not the issue here.  
In theory the search time should be shorter than the sum of the 2 cumulative values since I have more nodes than shard counts. So parallel processing is in place.

What do I make of this? Any suggestions on how to dig deeper? Thanks.

\*note: The profiler also takes multiple seconds to come back with the result. Not sure if it makes any difference here.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e83d3d368d8a46980f967c48f51b0f3bf97541ec.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/b/bb649993f906bb9e36e6c379dda2b26ccb5f8eb4.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/f/efc4eaf5b918619846f39b334e44be8f6415ea77.png)

---

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [October 19, 2021, 8:43pm UTC](https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770/2 "2021-10-19T20:43:34Z")

</div>

Nobody can shed some light on this?

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [October 20, 2021, 1:30pm UTC](https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770/3 "2021-10-20T13:30:46Z")

</div>

There was [a bug](https://github.com/elastic/elasticsearch/issues/75848) before 7.15 on wildcard field queries where profiled queries were faster than straight queries.

---

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [October 20, 2021, 8:06pm UTC](https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770/4 "2021-10-20T20:06:29Z")

</div>

ok. Thanks.  
I'll try again after upgrading to 7.15.0

I believe profiling using index alias also returns shorter time.

---

<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 17, 2021, 8:07pm UTC](https://discuss.elastic.co/t/kibana-search-profiler-accuracy/286770/5 "2021-11-17T20:07:25Z")

</div>

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