[t0mas88]

I've tested it, network latency is by far not as good as for example Rackspace Cloud. And tool-support is very far behind Amazon and OpenStack. Basically Google Compute Engine is something that might have had a chance years ago but at this point in time it's quite pointless because it has no upsides compared to existing far better established solutions and is behind on features, documentation, tools and user-support.

And I expect that not to get better soon if nobody is using it...

[ithkuil]

> And I expect that not to get better soon if nobody is using it...

If the people running GCE see that people are not using it because it sucks at X, they will probably do their best to address X. So complaining is a good thing, especially if it contains enough information in order to understand the problem (e.g. latency from/to where? internal network or external network?)

[dragonwriter]

> And I expect that not to get better soon if nobody is using it...

If Compute Engine is Google exposing internal infrastructure as an additional product, its quite likely that lots of people are using it (and that it is strategically important for it to be more usable) even if few people are paying for it.

[patrickaljord]

Google Compute Engine actually has many features that makes it better than AWS http://yourstory.com/2013/12/google-compute-engine-better-th...

[thrownaway2424]

Network latency to or from what?

[Florin_Andrei]

It's a lot easier to go from zero to proficient with GCE than it is with AWS. This has no relation with the fact that AWS has a bigger "menu".