# Recommended Elasticsearch Node requirements for monitoring 2000 nodes

**URL:** <https://discuss.elastic.co/t/recommended-elasticsearch-node-requirements-for-monitoring-2000-nodes/224057>\
**Category:** Metrics\
**Created:** [March 18, 2020, 9:25am UTC](https://discuss.elastic.co/t/recommended-elasticsearch-node-requirements-for-monitoring-2000-nodes/224057 "2020-03-18T09:25:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Bingu\_Shim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bingu_shim/32/57949_2.png) [@Bingu\_Shim](https://discuss.elastic.co/u/Bingu_Shim)\
**Post date:** [March 21, 2020, 2:56am UTC](https://discuss.elastic.co/t/recommended-elasticsearch-node-requirements-for-monitoring-2000-nodes/224057/4 "2020-03-21T02:56:15Z")

</div>

Hello @Kerry

Thank you for your response.  
With my configurations above, the number of documents written per minutes are as follow.

| event.dataset | docs per minutes |
| --- | --- |
| system.diskio | 6 |
| system.fsstat | 6 |
| system.load | 6 |
| system.uptime | 6 |
| system.cpu | 6 |
| system.memory | 6 |
| system.process.summary | 6 |
| system.network | 96 |
| total | 138 |

So, I can get required write performance as follow.

- 2.3 tps per 1 node
- 4,600 tps for 2,000 nodes.

This write load should be handled with our elasticsearch cluster. (I've done over 30K write performance test on our environment. The use cases was different though)

What I want to know is Metric UI sides latency.  
Since I got UI latency problem with using Elastic APM ([THIS ISSUE](https://discuss.elastic.co/t/kibana-apm-app-pages-are-too-slow/220570), [THIS ISSUE](https://discuss.elastic.co/t/apm-ui-kibana-internal-server-error/223601/21)), and found out the team just started [architectural improvement](https://github.com/elastic/apm-server/issues/3485) to solve latency problem.

So we just want to make it sure that scalability of Metric UI, before going further.

As you mentioned as follow, there won't be scalability problem with UI side.

> Serving 2,000 nodes in the UI shouldn't be a problem

We will trying to apply Metricbeat more machines.

---

_[View the full topic](https://discuss.elastic.co/t/recommended-elasticsearch-node-requirements-for-monitoring-2000-nodes/224057)._