# Using Digital Ocean Droplets as Client Nodes

**URL:** <https://discuss.elastic.co/t/using-digital-ocean-droplets-as-client-nodes/58297>\
**Category:** Elasticsearch\
**Created:** [August 17, 2016, 10:11pm UTC](https://discuss.elastic.co/t/using-digital-ocean-droplets-as-client-nodes/58297 "2016-08-17T22:11:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shabi](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@shabi](https://discuss.elastic.co/u/shabi)\
**Post date:** [August 17, 2016, 10:11pm UTC](https://discuss.elastic.co/t/using-digital-ocean-droplets-as-client-nodes/58297/1 "2016-08-17T22:11:39Z")

</div>

Would a small digital ocean droplet generally work well for a dedicated Kibana/Elasticsearch client node? Would a $20/month (2 GB RAM/2 CPU) work well in most circumstances? Would a $5/month (512 MB RAM/1 CPU) droplet even be viable? I’m unsure of the actual load that splitting search requests & combining/reducing results puts on a client node.

My planned setup is 4-6 ES data nodes (8 CPUs each, ~100 GB RAM total), indexes up to 1 TB each, each index with 1 shard per data node, and serving up dashboards potentially for up to a couple dozen people at a time.

---

<div class="post-metadata">

**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 17, 2016, 10:17pm UTC](https://discuss.elastic.co/t/using-digital-ocean-droplets-as-client-nodes/58297/2 "2016-08-17T22:17:36Z")

</div>

> [@shabi](#):
>
> Would a $5/month (512 MB RAM/1 CPU) droplet even be viable?

Nope.

> [@shabi](#):
>
> Would a $20/month (2 GB RAM/2 CPU) work well in most circumstances?

Depends how big your queries are.

---

<div class="post-metadata">

**Author:** ![shabi](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@shabi](https://discuss.elastic.co/u/shabi)\
**Post date:** [August 17, 2016, 11:12pm UTC](https://discuss.elastic.co/t/using-digital-ocean-droplets-as-client-nodes/58297/3 "2016-08-17T23:12:18Z")

</div>

So, RAM & CPU needs of a client node will mainly be determined by the amount of data the client node is handling in the search reduce/"gather phase" of a query, and the number of queries being performed simultaneously.

Is the work being performed during the gather phase on a client node comparable to or much less than the work performed while executing the query on one of the data nodes?

---

<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 5, 2017, 10:27pm UTC](https://discuss.elastic.co/t/using-digital-ocean-droplets-as-client-nodes/58297/4 "2017-07-05T22:27:07Z")

</div>


