# Elastic search 1.4.4 VS 2.4.0 performance

**URL:** <https://discuss.elastic.co/t/elastic-search-1-4-4-vs-2-4-0-performance/77592>\
**Category:** Elasticsearch\
**Created:** [March 7, 2017, 3:28am UTC](https://discuss.elastic.co/t/elastic-search-1-4-4-vs-2-4-0-performance/77592 "2017-03-07T03:28:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinoth\_es](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@vinoth\_es](https://discuss.elastic.co/u/vinoth_es)\
**Post date:** [March 7, 2017, 3:28am UTC](https://discuss.elastic.co/t/elastic-search-1-4-4-vs-2-4-0-performance/77592/1 "2017-03-07T03:28:11Z")

</div>

Executed a query in ES 1.4.4 and 2.4.0 the results shows 3x times performance degrade in 2.4.0 . Both 1.4.4 and 2.4.0 Hardware configurations and Shard configurations are same. Below is the query. Not sure missing any tuning configurations specific to 2.4.0

{  
"from" : 0,  
"size" : 200,  
"query" : {  
"bool" : {  
"must" : {  
"query\_string" : {  
"query" : "category:vehicles"  
}  
}  
}  
},  
"\_source" : {  
"includes" : ["@type", "name", "model", "year"],  
"excludes" : []  
},  
"aggregations" : {  
"results" : {  
"terms" : {  
"field" : "model",  
"size" : 200  
},  
"aggregations" : {  
"hits" : {  
"top\_hits" : {  
"size" : 20,  
"\_source" : {  
"includes" : ["@type", "name", "model", "year"],  
"excludes" : []  
},  
"highlight" : {  
"require\_field\_match" : false,  
"fields" : {  
"\*" : { }  
}  
}  
}  
}  
}  
}  
},

"highlight" : {  
"require\_field\_match" : false,  
"fields" : {  
"\*" : { }  
}  
}  
}

Tried the following optimization techniques no luck.

Tried mapping with doc value true for all fields  
Tried mapping doc value false for all fields  
"collect\_mode" algorithm set as Breadth first  
"collect\_mode" algorithm set as Depth first  
With global\_ordinals\_low\_cardinality enabled  
With eager loading of fields enabled & disabled  
Profiling the query to debug time taken for each part  
Increased query caching of ES server to upto 30%  
Scanning ES server for swap memory  
Monitoring ES server's CPU, Heap size and RAM  
Increased heap size from 50% of RAM upto 75%  
Tried using execution hint  
Tried executing query directly in ES server (to rule out n/w issues)  
Tried executing query in a single ES server instead of a cluster

---

<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:** [April 4, 2017, 3:28am UTC](https://discuss.elastic.co/t/elastic-search-1-4-4-vs-2-4-0-performance/77592/2 "2017-04-04T03:28:12Z")

</div>

Closed on April 4, 2017, 3:28am UTC

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