# Performance test 2.0 to 5.0 for server set up

**URL:** <https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373>\
**Category:** Elasticsearch\
**Created:** [February 4, 2018, 10:48pm UTC](https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373 "2018-02-04T22:48:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![0NE](https://avatars.discourse-cdn.com/v4/letter/0/898d66/32.png) [@0NE](https://discuss.elastic.co/u/0NE)\
**Post date:** [February 4, 2018, 10:48pm UTC](https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373/1 "2018-02-04T22:48:52Z")

</div>

Hello guys,

We are moving away from our legacy version of elasticsearch 2.0 (with marvel and alerting) to 5.0 with xpack.

I was wondering what is an easy and good way to performance test elastic? I want to see how it affects the performance from upgrading, and to see if the xpack plugin requires us to have a better servers because of the additional plugins.

Our server configuration as of now:

3x machines (1 node per machine) with 4 cores and 32GB of ram

I am looking to change that to:

each machine have 3 nodes, using containers. each node will have 2 cores and 9GB of RAM. What do you think?

---

<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:** [February 5, 2018, 12:28am UTC](https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373/2 "2018-02-05T00:28:40Z")

</div>

Why not go to 6.0?

Have you see Rally - [https://github.com/elastic/rally](https://github.com/elastic/rally) - it's for benchmarking Elasticsearch 🙂

---

<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:** [February 5, 2018, 6:22am UTC](https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373/3 "2018-02-05T06:22:57Z")

</div>

I do not see the point in having a larger number of smaller nodes on the same hardware as it increases overhead and complexity. The point where you start having more than 1 node per server is generally when you have more than 64GB RAM on the host and want to maximise heap space, which does not seem to be the case here.

---

<div class="post-metadata">

**Author:** ![0NE](https://avatars.discourse-cdn.com/v4/letter/0/898d66/32.png) [@0NE](https://discuss.elastic.co/u/0NE)\
**Post date:** [February 5, 2018, 10:38am UTC](https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373/4 "2018-02-05T10:38:14Z")

</div>

Out end goal is to be on 6.0. As we have set up 5.0 a month ago, we are just going to benchmark just to see how xpack affects the system.

Thank you for the rally recommendation!

Thanks for your help,

---

<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:** [March 5, 2018, 10:38am UTC](https://discuss.elastic.co/t/performance-test-2-0-to-5-0-for-server-set-up/118373/5 "2018-03-05T10:38:35Z")

</div>

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