21–30 of 33 posts
Earlier quoted context omitted.
How do people get beta access? I'd love to look at moving workloads over to GCE.
Sign up and let us know what you are looking to do. We are trickling out invites but being careful that we can deliver a great experience (support wise and otherwise) to everyone.
Earlier quoted context omitted.
In this case it means 8 cores/16 threads. Logging into a cc2.8xlarge instance shows 32 threads.
It sounds like EC2 and GCE are using different terminology here, so Google is giving you half as many cores as you think but thanks to Sandy Bridge they're crazy fast.
Earlier quoted context omitted.
Sign up and let us know what you are looking to do. We are trickling out invites but being careful that we can deliver a great experience (support wise and otherwise) to everyone.
A google product with a great support experience? This I gotta see.
Earlier quoted context omitted.
Not to worry it is confusing for everyone. My experience when drilling down on these things are that generally in marketing advertising literature a 'core' is what most people would call a 'thread.' Engineering documentation is usually more precise but when its perceived value, perception take priority over precision.
I'd love to hear what people think the standard nomenclature here is. I've been arguing with our PM as to call these things virtual cores or virtual CPUs. Our API uses guestCpus. This stuff is very confusing and I'd love to find the right way to communicate it clearly.
In the ideal world for a set of cores C if I run a piece of independent, memory bound, code on all of them I get O(C) scale. Generally that doesn't hold in shared L2/L3 cores or where HyperThreads are counted as cores.
We can define a scaling factor Cf such that 0 In one school you could price out at cores such that 1/Cf physical cores were assigned per Core purchased (rounded up to the nearest unit of computation) but that doesn't begin to get into the question of shared memory vs shared network vs shared disk.
I think the best you can do for now is call it a core if Cf is > .95.
Earlier quoted context omitted.
A google product with a great support experience? This I gotta see.
Like most things in life, you get better support when you pay for it.
I suspect they will do a decent job of supporting GCE, either through a premium offering themselves, or through third party developers -- same thing AWS has done. I had some meetings with AWS application/security platform consultants recently, and they do a really good job of it, you just have to pay for it.
This isn't a good argument for consumer products (if a random grandmother gets locked out of her gmail, and doesn't know anyone, she may be doomed), but I suspect any developer building products on GCE either knows someone or can pay for support, or can bitch in a high visibility forum and get help from third parties or by Google.
The comparison on cost is again on the EC2 on-demand pricing. Reserved pricing or spot pricing would cut that down substantially.