# Hardware suggestion

**URL:** https://discuss.elastic.co/t/hardware-suggestion/63989
**Category:** Logstash
**Created:** [October 26, 2016, 10:32am UTC](https://discuss.elastic.co/t/hardware-suggestion/63989 "2016-10-26T10:32:42Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Raj\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raj_kumar/32/25420_2.png) [@Raj\_Kumar](https://discuss.elastic.co/u/Raj_Kumar)
#### Post date: [October 26, 2016, 10:32am UTC](https://discuss.elastic.co/t/hardware-suggestion/63989/1 "2016-10-26T10:32:42Z")

</div>

Hi All,

Its been a few months we are using the ELK stack and its pretty amazing.We do planning to get commercial plugins which is seems to be awesome. So we thought we could implement with [Production.By](http://Production.By) seeing some blogs its been noticed and recommended to have cluster setup for elasticsearch for better performance.

We would like to have the syslog messages as central logging in ELK .We have around 600 devices, out of which 100 syslog servers and 500 switches with flows enabled.

Please anybody recommend the hardware requirements for this setup of around 50000 Messages per second in ELK and 40000 flows per second (in two different clusters)

Any feedbacks and suggestions would be really helpful 🙂

Thanks,  
Raj

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [October 26, 2016, 10:41am UTC](https://discuss.elastic.co/t/hardware-suggestion/63989/2 "2016-10-26T10:41:04Z")

</div>

Didn't you ask this exact question yesterday?

---

<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: [July 6, 2017, 4:32am UTC](https://discuss.elastic.co/t/hardware-suggestion/63989/3 "2017-07-06T04:32:40Z")

</div>


