# Range query speed very slow

**URL:** <https://discuss.elastic.co/t/range-query-speed-very-slow/46400>\
**Category:** Elasticsearch\
**Created:** [April 5, 2016, 1:51pm UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400 "2016-04-05T13:51:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![KennFalcon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kennfalcon/32/28460_2.png) [@KennFalcon](https://discuss.elastic.co/u/KennFalcon)\
**Post date:** [April 5, 2016, 1:51pm UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400/1 "2016-04-05T13:51:40Z")

</div>

I put about 1,000,000,000 data into a index of elasticsearch. The index has 10 shards. Each data has a field that is a time and the time is not analyzed. I range query data by the time. I use 100 threads to search it. The speed is very slow. Every thread cost about 10s. How can I deal with the problem?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 7, 2016, 1:06am UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400/2 "2016-04-07T01:06:56Z")

</div>

Can you provide a search example?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 7, 2016, 2:04am UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400/3 "2016-04-07T02:04:38Z")

</div>

How large are the shards? What is the specification of your cluster/machine? What is the query latency if you only use a single thread for querying? What is the query latency if you use 10 threads for querying?

---

<div class="post-metadata">

**Author:** ![KennFalcon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kennfalcon/32/28460_2.png) [@KennFalcon](https://discuss.elastic.co/u/KennFalcon)\
**Post date:** [April 7, 2016, 11:47am UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400/4 "2016-04-07T11:47:59Z")

</div>

Every shard had about 80G data.  
The cluster has two nodes. Every node is:

1. 3T SSD
2. 24 CPU，E5 2620 v2
3. 128G memory, I offered 64G for elasticsearch  
A single thread cost about 1s~2s.

---

<div class="post-metadata">

**Author:** ![KennFalcon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kennfalcon/32/28460_2.png) [@KennFalcon](https://discuss.elastic.co/u/KennFalcon)\
**Post date:** [April 7, 2016, 12:08pm UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400/6 "2016-04-07T12:08:52Z")

</div>

The example:

* * *

## RangeQueryBuilder rangeQueryBuilder = QueryBuilders.rangeQuery("time").from(1400000000).to(1500000000);

The time is absolute number of seconds. And the size I set was 1000.

---

<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:** [July 5, 2017, 11:01pm UTC](https://discuss.elastic.co/t/range-query-speed-very-slow/46400/7 "2017-07-05T23:01:33Z")

</div>