Google Compute Engine vs. Amazon EC2: Video Transcoding
11–20 of 33 posts
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#12Does 8 cores mean 8 cores or 4 cores/8 threads? The documentation is confusing.
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.
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#13Does 8 cores mean 8 cores or 4 cores/8 threads? The documentation is confusing.
In this case it means 8 cores/16 threads. Logging into a cc2.8xlarge instance shows 32 threads.
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#14Earlier quoted context omitted.
I'm the TL for Google Compute Engine. This isn't the performance we expect here and we will be looking in to see what is going on.
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.
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#15Does 8 cores mean 8 cores or 4 cores/8 threads? The documentation is confusing.
I'd love to make our docs more clear on this. If you have a pointer to what is confusing we'll fix it up.
To be clear, for every machine type, we are offering a HT per virtual CPU. So that means that an n1-standard-8 instance gets 4 physical cores and 8 hyperthreads. (We are also offering 3.75GB of RAM and ~440G of ephemeral disk per vCPU).
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#16Google cache: http://webcache.googleusercontent.com/search?q=cache:http://...
The actual page should be performing better now.
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#17Does 8 cores mean 8 cores or 4 cores/8 threads? The documentation is confusing.
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.
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#18How could transfers from Google to Amazon be so much faster than from Google to Google?
I'm the TL for Google Compute Engine. This isn't the performance we expect here and we will be looking in to see what is going on.
bummer :) don't you guys run perf. test with your biggest competitor before launch?
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#19Does 8 cores mean 8 cores or 4 cores/8 threads? The documentation is confusing.
I'd love to make our docs more clear on this. If you have a pointer to what is confusing we'll fix it up. To be clear, for every machine type, we are offering a HT per virtual CPU. So that means that an n1-standard-8 instance gets 4 physical cores and 8 hyperthreads. (We are also offering 3.75GB of RAM and ~440G of ephemeral disk per vCPU).
I assume GCE is based on a space-shared design (1:1 pinned vCPUs); if that's not correct then this becomes harder. On https://developers.google.com/compute/docs/instances#overvie... I see the term "Virtual Cores", but I don't want to hear about virtual cores. I want to know how many physical cores are backing the VM. (I don't find the term "logical core" further down the page helpful either.)
So I would say:
n1-standard-1: 1/2 physical core
n1-standard-2: 1 physical core
...
n1-standard-8: 4 physical cores
Re: Google Compute Engine vs. Amazon EC2: Video Transcoding
#20Does 8 cores mean 8 cores or 4 cores/8 threads? The documentation is confusing.
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.