# Elastic search on VM

**URL:** <https://discuss.elastic.co/t/elastic-search-on-vm/66819>\
**Category:** Elasticsearch\
**Created:** [November 22, 2016, 7:40am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819 "2016-11-22T07:40:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Srini12](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Srini12](https://discuss.elastic.co/u/Srini12)\
**Post date:** [November 22, 2016, 7:40am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/1 "2016-11-22T07:40:49Z")

</div>

Hi  
We have built elastic search index which is running nicely on our local servers, but  
once we move it to Azure (Virtual Machine), the same search is taking too long.

Any ideas ?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![JoarSvensson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joarsvensson/32/8740_2.png) [@JoarSvensson](https://discuss.elastic.co/u/JoarSvensson)\
**Post date:** [November 22, 2016, 7:45am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/2 "2016-11-22T07:45:02Z")

</div>

Please provide more information on the data indexed, the type of VM, Elasticsearch version etc etc. It's hard to give any hints without knowing more.

---

<div class="post-metadata">

**Author:** ![Srini12](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Srini12](https://discuss.elastic.co/u/Srini12)\
**Post date:** [November 22, 2016, 8:03am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/3 "2016-11-22T08:03:40Z")

</div>

Hi  
Thanks.  
We created index and wrote sql data into index (roughly 10 Mill documents). The VM is windows server 2012 system. Elastic version is 2.3.

---

<div class="post-metadata">

**Author:** ![Srini12](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Srini12](https://discuss.elastic.co/u/Srini12)\
**Post date:** [November 22, 2016, 8:30am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/4 "2016-11-22T08:30:45Z")

</div>

We have not used any special or different settings for installing on VM, do we need any special settings for VM?

---

<div class="post-metadata">

**Author:** ![JoarSvensson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joarsvensson/32/8740_2.png) [@JoarSvensson](https://discuss.elastic.co/u/JoarSvensson)\
**Post date:** [November 22, 2016, 8:44am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/5 "2016-11-22T08:44:32Z")

</div>

How much longer does a typical search take? Are you running Windows Server 2012 locally as well with same settings regarding memory etc?

If it's possible, move to ES 5.0.1 for general performance boosts.

---

<div class="post-metadata">

**Author:** ![Srini12](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Srini12](https://discuss.elastic.co/u/Srini12)\
**Post date:** [November 22, 2016, 8:58am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/6 "2016-11-22T08:58:35Z")

</div>

On VM normal search taking avg 30 seconds, on local servers it is 5-10 sec.  
Yes, using 2012 server on local machines as well.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 22, 2016, 9:15am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/7 "2016-11-22T09:15:54Z")

</div>

What instance type are you using on Azure? How does this compare to the specification of the local machine?

---

<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:** [December 20, 2016, 9:16am UTC](https://discuss.elastic.co/t/elastic-search-on-vm/66819/8 "2016-12-20T09:16:02Z")

</div>

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