# Benchmarks: VPS vs dedicated/bare metal?

**URL:** <https://meta.discourse.org/t/benchmarks-vps-vs-dedicated-bare-metal/56908>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [Février 4, 2017, 4:01 UTC](https://meta.discourse.org/t/benchmarks-vps-vs-dedicated-bare-metal/56908 "2017-02-04T16:01:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [Février 5, 2017, 9:05 UTC](https://meta.discourse.org/t/benchmarks-vps-vs-dedicated-bare-metal/56908/4 "2017-02-05T21:05:46Z")

</div>

I’d start by tuning PostgreSQL for 16GB of available memory and provisioning 3 unicorns per core (that’s _core_, not _hyperthread_ – so a total of 12). On a 32GB box, that _should_ leave you with about 8GB of RAM for Redis, disk cache, overhead, and “whoops that unicorn got a bit bigger than I was expecting”. Having 32-64GB of swap on hand, also, should go without saying.

Then, see what happens: if you seem to be bottlenecked on unicorns (and you’re not CPU bound), throw in a couple more. If your PostgreSQL queries start to chug, retune PostgreSQL to use a bit more RAM. At 39€/month, though, I’d _very_ quickly consider splitting DB and web if that one box started to feel overloaded. It’s almost too cheap not to.

---

_[View the full topic](https://meta.discourse.org/t/benchmarks-vps-vs-dedicated-bare-metal/56908)._