# Performance problems scroll search

**URL:** <https://discuss.elastic.co/t/performance-problems-scroll-search/52474>\
**Category:** Elasticsearch\
**Created:** [June 10, 2016, 7:29pm UTC](https://discuss.elastic.co/t/performance-problems-scroll-search/52474 "2016-06-10T19:29:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Felipe\_Santos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felipe_santos/32/3511_2.png) [@Felipe\_Santos](https://discuss.elastic.co/u/Felipe_Santos)\
**Post date:** [June 10, 2016, 7:29pm UTC](https://discuss.elastic.co/t/performance-problems-scroll-search/52474/1 "2016-06-10T19:29:23Z")

</div>

Hi, I am using elasticsearch 1.7.  
I have daily indexes when I do a search with scroll, with tree months de elasticsearch became too slow or not responsive.  
Take a look some graphs that I printed from Marvel from data nodes

3 Master  
Java Heap: 5GB  
2 CPUs, Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz  
RAM:7,5GB

3 data nodes  
Java Heap: 8GB  
2 CPUS : Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz  
RAM: 15GB

2 client nodes  
Java Heap: 5GB  
2 CPUs Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz  
RAM: 7,4GB

 ![](https://us1.discourse-cdn.com/elastic/original/2X/1/18377f43dd1c0438a2880910acabcb2c640e097b.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/9/96f1bacfc4fea5fe3050ac22b33e93b71e15752a.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/8/86011384a5ac7983240648f96777ec8b871fa73e.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/0/023dd1d89a787bb03b38fafa5182f4eb59b8ef6c.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/c/caedc0d7d808c4a77691cd3ad8454df96a9ccbda.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/4/46b460f6350d6d92f904249e6dc125c7b2fa3793.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/4/4d1dee48670ffacdf8a5c849f74ae088723d83d2.png)

What is the best approach, increase number of machines? Increase the machines sizes? change architecture of my solution?

My search

`{ "_source": { "exclude": ["entries.*.request.postData", "entries.*.response.content"] }, "query": { "bool": { "must": [{ "term": { "_entrypoint.id": 5 } }, { "term": { "_api.version.id": 1 } }, { "query_string": { "query": "1111111" } }, { "range": { "entries.entrypoint.startedDateTime": { "gt": "2016-06-01T03:00:00.000Z", "lte": "2016-06-09T13:05:00.000Z" } } }] } }, "sort": [{ "entries.entrypoint.startedDateTime": { "order": "desc" } }] }`

---

<div class="post-metadata">

**Author:** ![Felipe\_Santos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felipe_santos/32/3511_2.png) [@Felipe\_Santos](https://discuss.elastic.co/u/Felipe_Santos)\
**Post date:** [June 13, 2016, 1:28pm UTC](https://discuss.elastic.co/t/performance-problems-scroll-search/52474/2 "2016-06-13T13:28:42Z")

</div>

any tips?

---

<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, 10:44pm UTC](https://discuss.elastic.co/t/performance-problems-scroll-search/52474/3 "2017-07-05T22:44:19Z")

</div>


