# Msearch speed

**URL:** https://discuss.elastic.co/t/msearch-speed/117149
**Category:** Elasticsearch
**Created:** [January 26, 2018, 5:39am UTC](https://discuss.elastic.co/t/msearch-speed/117149 "2018-01-26T05:39:43Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![jdgenio](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jdgenio](https://discuss.elastic.co/u/jdgenio)
#### Post date: [February 7, 2018, 6:32am UTC](https://discuss.elastic.co/t/msearch-speed/117149/4 "2018-02-07T06:32:42Z")

</div>

On another note, our main problem still persists. Perhaps you can shed some light on it? I made a new topic.

Here is the link:

> [@Slow terms aggregation speed on ~130M documents](https://discuss.elastic.co/t/slow-terms-aggregation-speed-on-130m-documents/118759):
>
> Environment: ES version: 5.3 Data nodes: 3 We are trying to, through elasticsearch, provide users pregenerated suggestions based on the current dataset (130M documents). The target is to get all unique values of a certain field's property in a certain search. Let's say Field.Name.untouched. Here is the query: { "query":{ "match\_phrase":{ "\_all":"tilapia" } }, "\_source":[], "size":0, "aggregations":{ "suggestions":{ …

---

_[View the full topic](https://discuss.elastic.co/t/msearch-speed/117149)._