# Use multi\_search&sort&highlight on Windows, performance problem

**URL:** <https://discuss.elastic.co/t/use-multi-search-sort-highlight-on-windows-performance-problem/147443>\
**Category:** Elasticsearch\
**Created:** [September 5, 2018, 4:15pm UTC](https://discuss.elastic.co/t/use-multi-search-sort-highlight-on-windows-performance-problem/147443 "2018-09-05T16:15:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![withcancer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/withcancer/32/35221_2.png) [@withcancer](https://discuss.elastic.co/u/withcancer)\
**Post date:** [September 5, 2018, 4:15pm UTC](https://discuss.elastic.co/t/use-multi-search-sort-highlight-on-windows-performance-problem/147443/1 "2018-09-05T16:15:43Z")

</div>

Recently I tried to search some BT seed data on ES, which has about two million data.I want to full text search the **name** and **path** field.  
Here is my mapping:

```auto
    {
        "settings": {
            "number_of_shards": 1,
            "number_of_replicas": 2,
            "refresh_interval": "30s",
            "index.store.preload": [
                "nvd",
                "dvd",
                "tim",
                "doc",
                "dim"
            ]
        },
        "mappings": {
            "common": {
                "dynamic": false,
                "properties": {
                    "path_all": {
                        "type": "text"
                    },
                    "name": {
                        "type": "text",
                        "analyzer": "ik_max_word",
                        "search_analyzer": "ik_max_word"
                    },
                    "length": {
                        "type": "long"
                    },
                    "popularity": {
                        "type": "integer"
                    },
                    "create_time": {
                        "type": "date",
                        "format": "epoch_millis"
                    },
                    "files": {
                        "properties": {
                            "length": {
                                "type": "long"
                            },
                            "path": {
                                "type": "text",
                                "analyzer": "ik_max_word",
                                "search_analyzer": "ik_max_word",
                                "copy_to": "path_all"
                            }
                        }
                    }
                }
            }
        }
    }

```

I tried the following query on kibana:

```auto
POST torrent_info/common/_search
{
    "from": 0,
    "size": 10,
    "sort": [
        {
            "_score": "desc"
        },
        {
            "length": "desc"
        },
        {
            "popularity": "desc"
        },
        {
            "create_time": "desc"
        }
    ],
    "query": {
        "multi_match": {
            "query": "mp3",
            "fields": [
                "name",
                "path_all"
            ]
        }
    },
    "highlight": {
        "pre_tags": [
            "<strong>"
        ],
        "post_tags": [
            "</strong>"
        ],
        "fields": {
            "name": {}
        }
    }
}

```

I allocated 4G memory to ES，but I found that the average retrieval speed was above 1s, sometimes more than 1s.  
I hope someone can help me with 2 questions below:

1. Is there anything I can improve in my configuration, mapping?
2. Is it a good choice to use es on windows?

---

<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:** [October 3, 2018, 4:15pm UTC](https://discuss.elastic.co/t/use-multi-search-sort-highlight-on-windows-performance-problem/147443/2 "2018-10-03T16:15:44Z")

</div>

Closed on October 3, 2018, 4:15pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.