# Time Search with more node in one cluster

**URL:** <https://discuss.elastic.co/t/time-search-with-more-node-in-one-cluster/33699>\
**Category:** Elasticsearch\
**Created:** [November 4, 2015, 4:12am UTC](https://discuss.elastic.co/t/time-search-with-more-node-in-one-cluster/33699 "2015-11-04T04:12:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NgocPham](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ngocpham/32/6242_2.png) [@NgocPham](https://discuss.elastic.co/u/NgocPham)\
**Post date:** [November 4, 2015, 4:12am UTC](https://discuss.elastic.co/t/time-search-with-more-node-in-one-cluster/33699/1 "2015-11-04T04:12:39Z")

</div>

sorry, im newbie and i have one question.

i read in here [https://www.elastic.co/guide/en/elasticsearch/guide/current/\_scale\_horizontally.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/_scale_horizontally.html), it have :

- “Increasing the number\_of\_replicas to 2”, the blogs index now has  
nine shards: three primaries and six replicas. This means that we can  
scale out to a total of nine nodes, again with one shard per node.  
This would allow us to triple search performance compared to our  
original three-node cluster.

i tried index database about 7526 hits,5 shards with index ,2 replicas, 3 node in one cluster , and SearchResponse result have 1313 hits.

I realize time search with one node or 3 node is same( response.getTook().getNanos() ) ,search in 1 node faster than 2 node, search in 2 node faster than 3 node.

My question is : Why? How to get max performance like Guide elasticsearch?

My PC run ubuntu 13.10,memory 8G, Intel® Core™ i3-4130 CPU @ 3.40GHz × 4 and use SSD

Thanks for your help.😄

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [November 4, 2015, 3:49pm UTC](https://discuss.elastic.co/t/time-search-with-more-node-in-one-cluster/33699/2 "2015-11-04T15:49:42Z")

</div>

I think your benchmark has two problems:

- 7526 is so small that you're not really benchmarking search, just your network
- the important metric that the page you linked is about is not latency, but throughput: the number of requests per second that your cluster can handle.

---

<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:40pm UTC](https://discuss.elastic.co/t/time-search-with-more-node-in-one-cluster/33699/3 "2017-07-05T23:40:35Z")

</div>