# Just launched, search is much slower than our self hosted

**URL:** <https://discuss.elastic.co/t/just-launched-search-is-much-slower-than-our-self-hosted/149882>\
**Category:** Elasticsearch\
**Created:** [September 25, 2018, 5:46pm UTC](https://discuss.elastic.co/t/just-launched-search-is-much-slower-than-our-self-hosted/149882 "2018-09-25T17:46:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![horstuff](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@horstuff](https://discuss.elastic.co/u/horstuff)\
**Post date:** [September 25, 2018, 5:46pm UTC](https://discuss.elastic.co/t/just-launched-search-is-much-slower-than-our-self-hosted/149882/1 "2018-09-25T17:46:49Z")

</div>

Since we are on the lower account we get zero support, which for integration issues is stupid. My question is: can I switch deployment types on the fly, trying a different optimization setup other than the default "recommended" one that we are using? If I do try a different deployment, will I have to use a new endpoint and new credentials, or will everything just transfer over whenever i switch deployment types?

Edit: I fixed it by creating and populating a new east coast deployment, which is much faster (closer to our web server). I had to plug in new endpoint and password but no big deal. I then deleted the other deployment.

---

<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 23, 2018, 5:46pm UTC](https://discuss.elastic.co/t/just-launched-search-is-much-slower-than-our-self-hosted/149882/2 "2018-10-23T17:46:50Z")

</div>

Closed on October 23, 2018, 5:46pm UTC

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