# Docker swarm cluster optimization and ingest node **URL:** \ **Category:** Elasticsearch\ **Created:** [March 28, 2018, 2:28am UTC](https://discuss.elastic.co/t/docker-swarm-cluster-optimization-and-ingest-node/125840 "2018-03-28T02:28:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ram\_Ibaset](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ram_ibaset/32/27747_2.png) [@Ram\_Ibaset](https://discuss.elastic.co/u/Ram_Ibaset)\ **Post date:** [March 28, 2018, 2:28am UTC](https://discuss.elastic.co/t/docker-swarm-cluster-optimization-and-ingest-node/125840/1 "2018-03-28T02:28:02Z")
I have a docker swarm cluster setup with the following config: 1 Coordinating node 3 Master nodes 3 Data nodes 7 Logstash nodes each extracting data from a DB The performance however is pretty bad at the moment. I am getting an average of 2 seconds event if there is no result. I turned off logstash hoping to see better performance and no luck. Any tips to tweak the performance? I am running on a single node and that performs much better. Should I look to running it on bare metal instead of docker? Additionally, elastic forces me into adding an ingest node. Why? I have added node.ingest: true to the data nodes. Can someone explain? Is this optimal? Per documentation this is a lightweight logstash feature built into elasticsearch. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 25, 2018, 2:28am UTC](https://discuss.elastic.co/t/docker-swarm-cluster-optimization-and-ingest-node/125840/2 "2018-04-25T02:28:40Z")
Closed on April 25, 2018, 2:28am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.