# Multiget (mget) API performance

**URL:** <https://discuss.elastic.co/t/multiget-mget-api-performance/289813>\
**Category:** Elasticsearch\
**Created:** [November 22, 2021, 2:15pm UTC](https://discuss.elastic.co/t/multiget-mget-api-performance/289813 "2021-11-22T14:15:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 23, 2021, 12:22am UTC](https://discuss.elastic.co/t/multiget-mget-api-performance/289813/2 "2021-11-23T00:22:24Z")

</div>

> [@jon\_cabrera](#):
>
> Is this behavior normal?

Yep, because you're basically doing `N` gets, each of which take time to run and then be collated. And the overall response is only going to be as fast as the slowest one.

> [@jon\_cabrera](#):
>
> A small percentage (~1%) seem to have times between `200ms-2000ms` .  
> Is there a way to lower the times of these requests?

At a guess, that could be a cache miss. I am not sure you can do much about those tbh.

> [@jon\_cabrera](#):
>
> If I'm not mistaken, the `profile` API is only available for `_search` .

[Correct](https://www.elastic.co/guide/en/elasticsearch/reference/7.15/search-profile.html);

> Any `_search` request can be profiled by adding a top-level `profile` parameter:

---

_[View the full topic](https://discuss.elastic.co/t/multiget-mget-api-performance/289813)._