Skip to content

Instantly share code, notes, and snippets.

@gmemstr

gmemstr/Server Requirements.md

Last active March 12, 2017 20:55
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gmemstr/3b0d3310b7c08d346d20cd468d3183e4 to your computer and use it in GitHub Desktop.
Save gmemstr/3b0d3310b7c08d346d20cd468d3183e4 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Server Requirements.md

LFS

I'm looking for a reliable server, preferably from a reputable company.

I've looked at a few options but can't decide on one or another, so I figure I'll leave it to whoever reads this.

Requirements:

  • At least 4 cores
  • 4+ GB/RAM
  • Decent sized disk
  • 100 Up/Down network
  • High bandwidth limit

I'll be using this server for deploying instances of webapps (e.g Platypus) in Docker containers, and would like a decent number of cores for testing various concurrency methods in Python (my current project).

I've looked at DigitalOcean droplets, Vultr instances, OVH services, and Linode. Vultr and Linode both look very tempting for their core-to-price count, but DO looks great for expanding in the future (load balancers etc). DO and OVH seem a bit more expensive but a) I'm already a cusomter of OVH b) DO looks very well laid out and has a lot of bells and whistles I may (but probably won't) use. I would prefer bare-metal hardware, so DO etc. are sort of last resorts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment