# Node HW Versus Hits supported

**URL:** <https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242>\
**Category:** Elasticsearch\
**Created:** [July 23, 2018, 7:21pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242 "2018-07-23T19:21:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucas.alvarez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lucas.alvarez/32/33649_2.png) [@lucas.alvarez](https://discuss.elastic.co/u/lucas.alvarez)\
**Post date:** [July 23, 2018, 7:21pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/1 "2018-07-23T19:21:06Z")

</div>

Hello everybody!. I would like to know if there's a way to roughly estimate the maximum number of hits that a node will support based on its hardware (disk, memory and CPU).

Are there any formulas that I can use for this?

---

<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:** [July 23, 2018, 7:22pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/2 "2018-07-23T19:22:08Z")

</div>

No, you generally need to benchmark this as there are a wide range of parameters that will affect this.

---

<div class="post-metadata">

**Author:** ![lucas.alvarez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lucas.alvarez/32/33649_2.png) [@lucas.alvarez](https://discuss.elastic.co/u/lucas.alvarez)\
**Post date:** [July 23, 2018, 7:23pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/3 "2018-07-23T19:23:13Z")

</div>

Hello Christian! Thanks for your reply. Would you recommend me any software to accomplish this task?

---

<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:** [July 23, 2018, 7:25pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/4 "2018-07-23T19:25:39Z")

</div>

We often use Rally for this. [This webinar provides an introduction](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right) and you [can find the project on GitHub](https://github.com/elastic/rally).

---

<div class="post-metadata">

**Author:** ![lucas.alvarez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lucas.alvarez/32/33649_2.png) [@lucas.alvarez](https://discuss.elastic.co/u/lucas.alvarez)\
**Post date:** [July 23, 2018, 7:27pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/5 "2018-07-23T19:27:10Z")

</div>

Thank you very much Christian!. I will try it out and let you know 🙂

---

<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:** [July 23, 2018, 7:28pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/6 "2018-07-23T19:28:46Z")

</div>

You may benefit from the following resources too:

[https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)

[https://www.elastic.co/elasticon/conf/2018/sf/the-seven-deadly-sins-of-elasticsearch-benchmarking](https://www.elastic.co/elasticon/conf/2018/sf/the-seven-deadly-sins-of-elasticsearch-benchmarking)

---

<div class="post-metadata">

**Author:** ![lucas.alvarez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lucas.alvarez/32/33649_2.png) [@lucas.alvarez](https://discuss.elastic.co/u/lucas.alvarez)\
**Post date:** [July 23, 2018, 7:37pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/7 "2018-07-23T19:37:09Z")

</div>

Perfect!. Can it also be used for benchmarking Elastic 6.3.0? In the quick start of the GitHub Repo I see **version=6.0.0**.

---

<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:** [July 23, 2018, 7:39pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/8 "2018-07-23T19:39:07Z")

</div>

Yes. It generally always supports the newest versions as we use Rally to benchmark them before releasing.

---

<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:** [August 20, 2018, 7:39pm UTC](https://discuss.elastic.co/t/node-hw-versus-hits-supported/141242/9 "2018-08-20T19:39:13Z")

</div>

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