# Elasticsearch 2.4.6 Performance Optimizations
**URL:** https://discuss.elastic.co/t/elasticsearch-2-4-6-performance-optimizations/101791
**Category:** Elasticsearch
**Created:** [September 26, 2017, 6:55am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-6-performance-optimizations/101791 "2017-09-26T06:55:25Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@apenen](https://discuss.elastic.co/u/apenen)
#### Post date: [September 26, 2017, 6:55am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-6-performance-optimizations/101791/1 "2017-09-26T06:55:26Z")
Hi everyone!
We have 3 nodes with 64 Cores, 128Gb of RAM and 3TB on SSD.
We are receiving more than 1k log messages per second. And we have 1494 indexes opened with 5 shards per index.
On Logstash and marvel agent sometimes shows bulk problems.
¿How we can optimize our stack?
Thanks.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 26, 2017, 6:58am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-6-performance-optimizations/101791/2 "2017-09-26T06:58:44Z")
That sounds like an awful lot of shards for that cluster size and data volume. Read [this blog post about shards and sharding](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster), as it provides some practical guidelines.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 24, 2017, 6:58am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-6-performance-optimizations/101791/3 "2017-10-24T06:58:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.