# Choice of hosting solution (Vultr) **URL:** https://meta.discourse.org/t/choice-of-hosting-solution-vultr/172482 **Category:** Self-hosting **Tags:** hosting **Created:** [December 7, 2020, 11:39am UTC](https://meta.discourse.org/t/choice-of-hosting-solution-vultr/172482 "2020-12-07T11:39:06Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield) #### Post date: [December 7, 2020, 11:59am UTC](https://meta.discourse.org/t/choice-of-hosting-solution-vultr/172482/2 "2020-12-07T11:59:31Z")
> [@Almightybean](#): > > I think Discorse works mostly in single core, right? Not really, like all websites, there is immediate potential for a lot of concurrent requests. In my experience, Discourse spreads its load across available cores quite nicely. A good summary of this is here: > [@ScaleWay review?](https://meta.discourse.org/t/scaleway-review/40916/12): > > If you doubled or tripled(!) single-core CPU performance, you’d be reducing the page generation component of site load time by about the inverse ratio (double CPU → half the time; triple CPU speed → third of the time). Note that’s only one component of site load time – there’s still the client-side JS rendering and network latency, which is completely outside your control, as well as database request processing time, which is within your control, but is dominated by the speed of your disks, an… --- _[View the full topic](https://meta.discourse.org/t/choice-of-hosting-solution-vultr/172482)._