# Number of replicas and query speed

**URL:** <https://discuss.elastic.co/t/number-of-replicas-and-query-speed/6320>\
**Category:** Elasticsearch\
**Created:** [January 9, 2012, 10:03am UTC](https://discuss.elastic.co/t/number-of-replicas-and-query-speed/6320 "2012-01-09T10:03:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bogdanionescu](https://avatars.discourse-cdn.com/v4/letter/b/7cd45c/32.png) [@bogdanionescu](https://discuss.elastic.co/u/bogdanionescu)\
**Post date:** [January 9, 2012, 10:03am UTC](https://discuss.elastic.co/t/number-of-replicas-and-query-speed/6320/1 "2012-01-09T10:03:30Z")

</div>

Hello

I have a 4 node cluster with 7.7M docs indexed. 5 shards.  
Fist I've tried with 1 replica (default config) and we tested the query  
speed. It worked fine.  
The we used the REST API to increase the number of replicas to 4 and after a  
while the nodes reflected this change (in shards dirs stored locally all had  
a copy of all the 5 shards).  
The problems is that the query speed was exactly the same as when using 1  
replica config!  
Any ideas why this happens? Shouldn't be any improvement at all?

--  
View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/number-of-replicas-and-query-speed-tp3644170p3644170.html](http://elasticsearch-users.115913.n3.nabble.com/number-of-replicas-and-query-speed-tp3644170p3644170.html)  
Sent from the ElasticSearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![medcl\_net](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@medcl\_net](https://discuss.elastic.co/u/medcl_net)\
**Post date:** [January 11, 2012, 6:24am UTC](https://discuss.elastic.co/t/number-of-replicas-and-query-speed/6320/2 "2012-01-11T06:24:00Z")

</div>

kimchy already said ,you reach the max performance with 4 box, the idea of  
replica is to make index available on more machine,if you have more box,and  
increase the replica, you will have more restful endpoints to perform the  
search.and then scales out.

-----Original Message-----  
From: bogdanionescu  
Sent: Monday, January 09, 2012 6:03 PM  
To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
Subject: number of replicas and query speed

Hello

I have a 4 node cluster with 7.7M docs indexed. 5 shards.  
Fist I've tried with 1 replica (default config) and we tested the query  
speed. It worked fine.  
The we used the REST API to increase the number of replicas to 4 and after a  
while the nodes reflected this change (in shards dirs stored locally all had  
a copy of all the 5 shards).  
The problems is that the query speed was exactly the same as when using 1  
replica config!  
Any ideas why this happens? Shouldn't be any improvement at all?

--  
View this message in context:  
[http://elasticsearch-users.115913.n3.nabble.com/number-of-replicas-and-query-speed-tp3644170p3644170.html](http://elasticsearch-users.115913.n3.nabble.com/number-of-replicas-and-query-speed-tp3644170p3644170.html)  
Sent from the ElasticSearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<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 6, 2017, 3:43am UTC](https://discuss.elastic.co/t/number-of-replicas-and-query-speed/6320/3 "2017-07-06T03:43:10Z")

</div>