# Cluster vs single node **URL:** \ **Category:** Elasticsearch\ **Created:** [August 6, 2014, 6:20pm UTC](https://discuss.elastic.co/t/cluster-vs-single-node/19123 "2014-08-06T18:20:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Geoff1](https://avatars.discourse-cdn.com/v4/letter/g/9fc29f/32.png) [@Geoff1](https://discuss.elastic.co/u/Geoff1)\ **Post date:** [August 6, 2014, 6:20pm UTC](https://discuss.elastic.co/t/cluster-vs-single-node/19123/1 "2014-08-06T18:20:02Z")
Hi, First I will apologize for most likely a naive question. I am currently building out our elasticsearch implementation from a single node, to a 3 node cluster. I have followed most of the tutorials I have found on the internet, but it seems my cluster is slower by up to 3x versus the single node we are currently using. When I do a search on our cluster, I see all the drives get pegged to 100% utilization, and the iowait gets up to around 70 on each node. When I do the same query on the single node, I don't even see a hit to the disk, and very little cpu. Here is our current setup in AWS: single node: m3.large 1 750GB 200 PIOPS drive elasticserch 0.90.7 Cluster: 3 c3.xlarge 1 200GB 400 PIOPS drive elasticsearch 1.2.2 The data for the cluster is spread across all 3 nodes, and I mean each node has the complete set of the data. The single node is using all default configuration, but the cluster nodes are just using these added configs: 'cluster.routing.allocation.node\_initial\_primaries\_recoveries' =\> '4' 'cluster.routing.allocation.node\_concurrent\_recoveries' =\> '2' 'indices.recovery.max\_bytes\_per\_sec' =\> '20mb' 'indices.recovery.concurrent\_streams' =\> '5' 'index.number\_of\_replicas' =\> '2' Are there any other configuration options I should add to get better search performance? Thank you for your time. Geoff ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 7, 2014, 8:18am UTC](https://discuss.elastic.co/t/cluster-vs-single-node/19123/2 "2014-08-07T08:18:48Z")
What sort of data are you searching and what sort of searches are they against it? Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 7 August 2014 04:20, Geoff [geoffreyowen@gmail.com](mailto:geoffreyowen@gmail.com) wrote: > Hi, > > First I will apologize for most likely a naive question. I am currently > building out our elasticsearch implementation from a single node, to a 3 > node cluster. I have followed most of the tutorials I have found on the > internet, but it seems my cluster is slower by up to 3x versus the single > node we are currently using. When I do a search on our cluster, I see all > the drives get pegged to 100% utilization, and the iowait gets up to around > 70 on each node. When I do the same query on the single node, I don't even > see a hit to the disk, and very little cpu. Here is our current setup in > AWS: > > single node: > > m3.large > 1 750GB 200 PIOPS drive > elasticserch 0.90.7 > > Cluster: > > 3 c3.xlarge > 1 200GB 400 PIOPS drive > elasticsearch 1.2.2 > > The data for the cluster is spread across all 3 nodes, and I mean each node > has the complete set of the data. The single node is using all default > configuration, but the cluster nodes are just using these added configs: > > 'cluster.routing.allocation.node\_initial\_primaries\_recoveries' =\> '4' > 'cluster.routing.allocation.node\_concurrent\_recoveries' =\> '2' > 'indices.recovery.max\_bytes\_per\_sec' =\> '20mb' > 'indices.recovery.concurrent\_streams' =\> '5' > 'index.number\_of\_replicas' =\> '2' > > Are there any other configuration options I should add to get better search > performance? > > Thank you for your time. > > Geoff > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Cluster-vs-single-node-tp4061375.html](http://elasticsearch-users.115913.n3.nabble.com/Cluster-vs-single-node-tp4061375.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/1407349203339-4061375.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1407349203339-4061375.post%40n3.nabble.com) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624a3Ef%2B7Ax9anUGaDdr1aZKGsRxccsJBiJskECWUwWJcHA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624a3Ef%2B7Ax9anUGaDdr1aZKGsRxccsJBiJskECWUwWJcHA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:10am UTC](https://discuss.elastic.co/t/cluster-vs-single-node/19123/3 "2017-07-06T01:10:15Z")