By the Numbers: How Google Compute Engine Stacks Up To Amazon EC2
vu1986 writes "Google launched its EC2 rival, Google Compute Engine, last June, it set some high expectations. Sebastian Standil's team at Scalr put the cloud infrastructure service through its paces — and were pleasantly surprised at what they found. A note about our data: The benchmarks run to collect the data presented here were taken twice a day, over four days, then averaged. When a high variance was observed, we took note of it and present it here as intervals for which 80 percent of observed data points fall into."
I look forward to seeing Amazon and Google battle each other in providing Linux infrastructure. I know there are many excellent small providers, but no one has really come close to Amazon so far.
I'd be far less trusting of Google when it comes to running every single analytic it knows of over my data. Amazon's got far less stake in regular data processing, they just want to know about shopping habits.
Benchmarks seemed to include everything but actual CPU (GFLOPS, Linpack, whatever) performance.
I would hazard a guess that pure number-crunchers use less general-purpose farms (and probably farms of graphic coprocessors).
You mean a cloud service in "limited preview" is much faster than a cloud server open to the public and heavily used?
There much be some fancy engineering behind the scenes to make a lightly used service run faster than a heavily used one.
I want to see the benchmarks after GCE is open to the public.
Twice a day over 4 days ... 8 samples ... this is supposed to be useful in some way?
You should be ashamed of yourself for presenting this data as if it has some sort of meaning at all, let alone a useful one.
You're going to need a couple orders of magnitude more samples before you even start thinking about being any sort of useful metric.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
paid service shutdown?
how about picasa.
google is not trying to hook people, but I still fail to understand why they shut down reader. It added a lot of value.
It is fast because nobody is using it.
google is a company. Companies don't really intrinsicaly about value provided to users as a rule. They care about the revenue they can get from their user activity. Reader porvides value, but Google seemingly doesn't see it as a revenue stream.
Google isn't doing things out of the goodness of their hearts. A lot of companies give that impression as they ramp up, but inevitably a company will show it's capitalist nature, fail as a business, or both.
XML is like violence. If it doesn't solve the problem, use more.
Do you think AWS will continue if it's eventually found to be nonprofitable?
Why is that ironic? The difficulty/pain for each of them to support the "other" OS isn't the same.
Linux is easier for cloud providers. eg no license tracking, billing or activation type stuff (for most distros at least) to worry about, small Linux server instances require less resources than Windows, just a bunch of files to deploy - no installation processes, instance specific UUIDs etc
Windows is harder (for everyone but MS) for the opposite reasons.