|
|
|
|
|
by itsfatz
2877 days ago
|
|
Ages ago I spun an aws instance w/ Grid, setup VPN and used Steam in-home streaming to accomplish a similar result. Using spot-instances resulted in something like $0.06/hr if memory serves (which it seldom does). Biggest caveats at that time were setup time and latency; since I was too cheap to preserve the instance volume and too lazy to split the steam save folder to a smaller separate volume, and had yet to secure gigabit fiber. It was more of a dalliance for me since I don't game often anymore, and if I'm honest with myself I enjoyed setting up the infrastructure more than I did playing Fallout 4. Please note this has more to do with how little fun I am in my old age than any problems with the game. |
|
Google Cloud can allow you to get the cost lower (closer to ~$0.15/hr) by cost optimizing the instance CPU/Memory and attaching a GPU to it.
But you've got three problems with both of these setups:
- Spot on AWS/Preemptible on GCP will kill your instance with about 2 minutes of warning. I'm not sure what AWS's policy is on how often this happens, but on GCP, its guaranteed to happen at least once every 24 hours. So that could be annoying if you're in the middle of an intense game of Overwatch.
- Storage costs. You're paying per hour for your instance, so you don't want to have to download all your games every time you spin it up. But, then you shift the cost to the SSD, which is expensive and must be maintained 24/7/365 for that quick startup time. You could alternatively store it in S3/GCS then hot-load it when the instance starts, which would be fast due to the fiber interconnect all these datacenters are wired with. So, plan for this bullet to add at least $10/mo/TB of storage.
- Network costs. A 1080p60 stream is, conservatively, 10Mbps? Add on an extra ~$0.25 per hour you want to game, just in bandwidth.