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
Sent from the ElasticSearch Users mailing list archive at Nabble.com.

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
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
Sent from the ElasticSearch Users mailing list archive at Nabble.com.