41–50 of 98 posts
Any reason you couldn't use these for conventional web stuff? 30 seconds could easily be long enough to bring up another instance and sync data if needed.
Any developer who was burned by App Engine pricing in the past is likely to take the lure of a "70% off" discount with a grain of salt because of the much higher cost of incorrectly relying on Google's pricing pledges. In case anyone forgets, the pricing changes on Google App Engine caused many developers to abandon apps they had developed on the platform because of hundreds of percent increases in pricing: https://g…
So... this is essentially first come, first served based on their description. And they say the preemptibles come from a smaller pool of resources. Seems odd to me they wouldn't have a number somewhere of how many are available and how many are in use given that it's a finite resource. Tough to build a business model around a resource you can't even determine the availability of.
That's exactly why it's cheap: you're trading price for reliability.
So... this is essentially first come, first served based on their description. And they say the preemptibles come from a smaller pool of resources. Seems odd to me they wouldn't have a number somewhere of how many are available and how many are in use given that it's a finite resource. Tough to build a business model around a resource you can't even determine the availability of.
Any reason you couldn't use these for conventional web stuff? 30 seconds could easily be long enough to bring up another instance and sync data if needed.
You'd have to make sure that if a node gets terminated while processing a request, that request can be re-routed to a live VM. Unless you don't care about users randomly seeing errors of course.
Any developer who was burned by App Engine pricing in the past is likely to take the lure of a "70% off" discount with a grain of salt because of the much higher cost of incorrectly relying on Google's pricing pledges. In case anyone forgets, the pricing changes on Google App Engine caused many developers to abandon apps they had developed on the platform because of hundreds of percent increases in pricing: https://g…
App Engine was in preview when its price changed.
During those 3 years no warning was given that the pricing changes were going to be of such a magnitude.
As a result people had sufficient time and not enough warning to build entire businesses on an infrastructure that they later had to abandon.
That's unforgivable.
Any developer who was burned by App Engine pricing in the past is likely to take the lure of a "70% off" discount with a grain of salt because of the much higher cost of incorrectly relying on Google's pricing pledges. In case anyone forgets, the pricing changes on Google App Engine caused many developers to abandon apps they had developed on the platform because of hundreds of percent increases in pricing: https://g…
That goes back to 2011. Has anything been changed on people more recently?
Any reason you couldn't use these for conventional web stuff? 30 seconds could easily be long enough to bring up another instance and sync data if needed.
Earlier quoted context omitted.
Well, spot varies. Sometimes it's low, but the price varies based on demand. Using prices as of right now for example, Currently in California, c3.8xl instances are quite popular, running $1.68 an hour on an instance that's normally 1.912 an hour, roughly a 13% discount. 70% strikes me as better than 13%, especially when it's predictable. (and 70% below an already substantially lower hourly price...) [1] http://stora…
The long-run price for a c3.8xlarge in California is somewhere between $0.40 and $0.50, though you're correct that right now they're $1.68. California tends to be more expensive than other AWS regions, though (I can't remember the reason - perhaps just availability?). If you're in us-east-1 the price sticks around $0.20 per hour, and eu-west-1 is rock-solid at $0.32 per hour. If you have work that can be done on spot…
For example, with Google you don't need to get a specialized instance type to use it's monster-fast Local SSD - just use the same instance types. This alone should simplify use of Preemptible VMs.