# Multisearch vs multiple search requests **URL:** \ **Category:** Elasticsearch\ **Created:** [January 6, 2016, 5:38pm UTC](https://discuss.elastic.co/t/multisearch-vs-multiple-search-requests/38526 "2016-01-06T17:38:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dorr](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@dorr](https://discuss.elastic.co/u/dorr)\ **Post date:** [January 6, 2016, 5:38pm UTC](https://discuss.elastic.co/t/multisearch-vs-multiple-search-requests/38526/1 "2016-01-06T17:38:28Z")
Hello, I have _k_ queries to do, each one of them gets a few records for some ID. The only difference is the filter value which is the ID. Is there any performance benefit to running a multisearch query (bulk) that contains all _k_ queries, versus just making _k_ single search calls to Elasticsearch? Thanks. ---
**Author:** ![bleskes](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@bleskes](https://discuss.elastic.co/u/bleskes)\ **Post date:** [January 6, 2016, 7:30pm UTC](https://discuss.elastic.co/t/multisearch-vs-multiple-search-requests/38526/2 "2016-01-06T19:30:30Z")
The msearch just save on some coordination on your end. All it does is send the requests together to a single node, make the requests in parallel for you and returns the results. ---
**Author:** ![panda2004](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/panda2004/32/19473_2.png) [@panda2004](https://discuss.elastic.co/u/panda2004)\ **Post date:** [June 23, 2017, 11:49am UTC](https://discuss.elastic.co/t/multisearch-vs-multiple-search-requests/38526/3 "2017-06-23T11:49:26Z")
Another question in the same topic: 1. It's really interesting to know how Kibana addresses this situation. Aftera ll, one dashboard contains K graphs. Does it sends all the requests in multi search API or one by one? 2. What exactly the max\_concurrent\_searches parameter does? As far as my understanding - using multi search could even be worse for some situations. Instead of dividing the K search requests between all available nodes, and therefore getting a real parallel experience, we are using only one available coordinating node. On the other hand, in the customer retrospective who wait for ALL the requests to return - this might lead the cluster to make the requests in the right order. Pretty confusing, ha? 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 4:12am UTC](https://discuss.elastic.co/t/multisearch-vs-multiple-search-requests/38526/4 "2022-11-04T04:12:18Z")