# Multisearch query performance

**URL:** <https://discuss.elastic.co/t/multisearch-query-performance/36956>\
**Category:** Elasticsearch\
**Created:** [December 11, 2015, 9:14am UTC](https://discuss.elastic.co/t/multisearch-query-performance/36956 "2015-12-11T09:14:04Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [December 11, 2015, 10:46am UTC](https://discuss.elastic.co/t/multisearch-query-performance/36956/4 "2015-12-11T10:46:41Z")

</div>

> [@Anatoly\_Petkevich](#):
>
> Actually we have 3 nodes, 7 primary shards with one replica.

Oh ok I misunderstood `replicas - 1` 🙂

If you're using an official client to connect to your cluster you can execute your requests and let the client act as a kind of load balancer between your nodes. You can also try to use routing.

---

_[View the full topic](https://discuss.elastic.co/t/multisearch-query-performance/36956)._