4 ms·
Reminds me of a time, we had a new site that was going to run on GCP, we had been using a couple co-located servers for years. When everything was moved to pro
by bluedino 5y ago
Reminds me of a time, we had a new site that was going to run on GCP, we had been using a couple co-located servers for years.
When everything was moved to production, URL went live, nobody ever did any kind of bandwidth checking, caching, no CDN, no cost tracking. $10,000 in our first week. That's about 1/4 what our total spend on the co-located servers was for the whole year. Boss flipped his lid and wanted to kill the new guy who was on the project.
After about 2 years we got rid of all the co-located stuff and were spending about 1.5x, but we had more apps, they served heavier pages, etc.
- dijit 5y ago1.5x is pretty good. We overspent quite heavily on our on-prem stuff for a game I helped launch, for political reasons the next game ended up running on the cloud. The price was roughly 10x before discounts. With our heavy discounts and a wide amount of slimming down/cost optimisation (easily 3 months of work) we got it to 2.3x There will always be a need for sysadmins/cloudops/devops for that environment, so we didn't save any headcount either. I can't imagine getting anywhere close to parity in costs, Functions-as-a-service ended up costing more than compute instances too so we went back to compute instances in places where we thought we'd get away from it. That said, it was a lot nicer to use!
- hogrider 5y agoAwful toxic boss.