# Query latency/service time are always identical

**URL:** <https://discuss.elastic.co/t/query-latency-service-time-are-always-identical/313477>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [September 1, 2022, 7:34pm UTC](https://discuss.elastic.co/t/query-latency-service-time-are-always-identical/313477 "2022-09-01T19:34:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmlucjav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmlucjav/32/5870_2.png) [@jmlucjav](https://discuss.elastic.co/u/jmlucjav)\
**Post date:** [September 1, 2022, 7:34pm UTC](https://discuss.elastic.co/t/query-latency-service-time-are-always-identical/313477/1 "2022-09-01T19:34:33Z")

</div>

Hi,

in all my benchmarks, these values are always the same:

| 50th percentile latency | replay-listing-query | 4.3336 | ms |  
| 90th percentile latency | replay-listing-query | 44.9377 | ms |  
| 99th percentile latency | replay-listing-query | 249.982 | ms |  
| 50th percentile service time | replay-listing-query | 4.3336 | ms |  
| 90th percentile service time | replay-listing-query | 44.9377 | ms |  
| 99th percentile service time | replay-listing-query | 249.982 | ms |

It is too much of a coincidence no??

thanks

---

<div class="post-metadata">

**Author:** ![RickBoyd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rickboyd/32/80022_2.png) [@RickBoyd](https://discuss.elastic.co/u/RickBoyd)\
**Post date:** [September 1, 2022, 7:50pm UTC](https://discuss.elastic.co/t/query-latency-service-time-are-always-identical/313477/2 "2022-09-01T19:50:34Z")

</div>

Hi!

I'm assuming you mean that "latency" and "service time" are always the same for each percentile, not that you get the exact same values in your results between each run.

This is the expected outcome when you run tasks without a `target-throughput`. See the FAQ for more info: [Frequently Asked Questions (FAQ) - Rally 2.6.0 documentation](https://esrally.readthedocs.io/en/stable/faq.html#what-do-latency-and-service-time-mean-and-how-do-they-relate-to-the-took-field-that-elasticsearch-returns)

---

<div class="post-metadata">

**Author:** ![jmlucjav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmlucjav/32/5870_2.png) [@jmlucjav](https://discuss.elastic.co/u/jmlucjav)\
**Post date:** [September 1, 2022, 8:07pm UTC](https://discuss.elastic.co/t/query-latency-service-time-are-always-identical/313477/3 "2022-09-01T20:07:45Z")

</div>

makes sense, thanks Rick!

---

<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:** [September 29, 2022, 8:08pm UTC](https://discuss.elastic.co/t/query-latency-service-time-are-always-identical/313477/4 "2022-09-29T20:08:29Z")

</div>

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