31–40 of 149 posts
Earlier quoted context omitted.
If you're concerned about cost, AWS is almost never the right place to host to begin with.
You miss the point. The lifetime of a web request, for example, can be measured in milliseconds. It is now possible, technically anyway, for operating systems to boot, service the request and disappear. There needs to be pricing models that reflect computing models like this.
Earlier quoted context omitted.
Sounds like you're describing AWS Lambda / serverless architecture. But maybe I'm not understanding your use case?
There are a wide range of tiny operating systems that can boot in a matter of milliseconds. The applications are "whatever you want imagine" but yes one application is building FAAS Function As A Service in which the operating system carries out a single function. Put anther way, Docker is complex, overweight, and requires re-implementation of much computing infrastructure. You can meet many of the same goals as Dock…
Per-second billing greatly reduces the overhead to bringing up an instance for a short task then killing it immediately - so I can do that. There's no need to build a buffer layer to add workers to a pool and leave them in the pool, so that you didn't end up paying for 30 hours of instance time to run 30, two-minute tasks within an hour.
The exception is Google Compute has a 10 minute minimum, so if you are creating machines and destroying them quickly, per second billing will be noticeable.
Per second billing is somewhat of a gimmick just so Amazon can say they are more granular than Google Compute. The difference between seconds and a minute of billing is fractions of a cent. Rounding errors. The exception is Google Compute has a 10 minute minimum, so if you are creating machines and destroying them quickly, per second billing will be noticeable.
Earlier quoted context omitted.
If you're concerned about cost, AWS is almost never the right place to host to begin with.
You miss the point. The lifetime of a web request, for example, can be measured in milliseconds. It is now possible, technically anyway, for operating systems to boot, service the request and disappear. There needs to be pricing models that reflect computing models like this.
That's sure nice, but I'm waiting for AWS to switch to automatic sustained use discounts [0] like GCP offers. [0]: https://cloud.google.com/compute/docs/sustained-use-discount...
I'm waiting for GCP to support preemptible GPU instances. Would love to be able to spend ~50% less on GPU instances when running a batch job that can be stopped and reloaded.
Likely due to GCP competition. I believe GCP was always per-second? [Edit: Misremember that, they were always per-minute. Lots of good information below directly form the related parties.] Azure looks to be per-hour [Edit: Wrong again, they are per-minute as well. Oddly enough, I did check their pricing page before, but missed the per-minute paragraph and only saw the hourly pricing] but I'm seeing something about co…
GCP VMs are per-minute, with a minimum of 10 minutes (vs AWS' new minimum of 1 minute). Second resolution is nice, but I doubt it makes much difference in pricing for most workloads. https://cloud.google.com/compute/pricing#billingmodel Azure's containers don't use a full VM-- they're more like AWS Lambda or other serverless frameworks, so they do per-second billing with no minimums. Disclaimer: I work at Google on C…
Earlier quoted context omitted.
I'm waiting for GCP to support preemptible GPU instances. Would love to be able to spend ~50% less on GPU instances when running a batch job that can be stopped and reloaded.
Not sure that will happen anytime soon. It's the same with Local SSD. The virtualization of this environment is very challenging, maybe beyond a point where it makes sense for them to do so.