# Simple queries takes lots of time and uses 100% cpu

**URL:** <https://discuss.elastic.co/t/simple-queries-takes-lots-of-time-and-uses-100-cpu/206243>\
**Category:** Elasticsearch\
**Created:** [November 2, 2019, 3:06pm UTC](https://discuss.elastic.co/t/simple-queries-takes-lots-of-time-and-uses-100-cpu/206243 "2019-11-02T15:06:13Z")\
**Posts on this page:** 1\
**Showing post:** 27

<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:** [November 14, 2019, 12:09pm UTC](https://discuss.elastic.co/t/simple-queries-takes-lots-of-time-and-uses-100-cpu/206243/27 "2019-11-14T12:09:13Z")

</div>

> [@aimarjg](#):
>
> about replicas used - It's a single node with 5 shards and just 1 replica so I believe it does not matter, does it?

If you only have a single node you'll never get any replicas (there's no added resilience or throughput benefits in allocating replica shards to the same node as the primary shard).

So I guess we can rule out any `preference` difference between Discover and Console.

It might be worth noting [Kibana's description of timings](https://discuss.elastic.co/t/what-is-query-duration-and-request-duration-in-kibana/50553). I wonder if there's added overhead in the unpacking of all that JSON in the 500 doc results (did we already establish performance was linear with the `size` setting for hits?)

---

_[View the full topic](https://discuss.elastic.co/t/simple-queries-takes-lots-of-time-and-uses-100-cpu/206243)._