Amazon Makes It Almost Impossible To Calculate Their "Virtual CPU" Equivalent (informationweek.com)
dkatana writes: AWS started out defining its virtual CPUs as being composed of EC2 compute units, or ECUs, which it defined as an equivalent to a physical Xeon processor. However, a virtual CPU now looks suspiciously variable... A virtual CPU is whatever Amazon wants to offer in an instance series. The user has no firm measure to go by. From the article:
[B]y doing a little math, you could actually compare what you were getting in virtual CPUs in EC2 versus Azure. Also by doing a little math, you knew how to compare one Amazon instance to another based on the ECU count in each virtual CPU. Microsoft didn't look too bad in the comparison.
That is one of the casualties of the nomenclature change.
I have searched for updated information on how a virtual CPU is measured and found nothing comparable to the definition of the 2012 ECU measure. I have questioned Amazon representatives three times between Oct. 27 and Dec. 21, and don't have much of an answer."
In fact Amazon doesn't know themselves... I have asked them to compare to the i7 series and they simply don't have a clue.
If you don't like it use something else
Who cares? Your stuff is gonna get hacked anyways and the Internet (in the US) is slower than dirt due to crappy ISP throttling.
Most people don't care about the exact performance, so it's not with spending the money and effort to precisely define or guarantee it.
Amazon is generic and cheap. Microsoft has really good integration with visual studio and .NET. Those are the factors people choose by.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
I read this a they're worth whatever they say it's worth (at the moment) and you're going to whine and complain about it but, not do anything about it. Until they start loosing a large dollar value of customers over it, they're not going to fix it.
"Be particularly skeptical when presented with evidence confirming what you already believe." -
that the "Cloud" is nebulous....
Imho there is only 1 valid measurement for cloud solutions, how much will certain performance cost you. And you can only really find out by testing it for _your_ specific goal. Some apps require more cpu, others more disk, others more ram... there's no single number to indicate your price/performance index.
then buy dedicated instances.
I like micro instances/instances which do not occupy full physical processors at Amazon because of availability and price for low-impact/bandwidth applications. For all other use lambda or dedicated instances.
Virtual CPUs are anyway difficult to asses - to me it may be very relevant to have the 1st level cache of the core which i run on undisturbed by other applications (since changing the cache hits is a big deal for specific numerical problems), and for you 20% more share of the CPU may be important.
1% of computation time not spend in my task on a physical processor can do as much damage as 50% change in speed.
A small side remark: the price for the different VCPUs also varies.
beg for CPU time and be happy when the admins throw you a little bone just like back in the 70's
The 'bursting' nature of the new AWS specs are straightforward enough: if your application is 'bursty' in nature - that is, it wants bursts of CPU power between long idle intervals - then the shared vCPU options are viable and while you're running your spec might very well exceed that of an ages-old 1GHz Xeon processor.
But specs are a difficult thing to nail down: are you focused on matching the math processing specs of the old processor? The I/O specs? Do you expect a more modern CPU to be slowed down so that your application takes the same amount of time to execute as it would on a Xeon?
Personally, I'd rather my application complete serving a web page five times faster, then sit idle for four times as long (while the hypervisor has the CPU off serving other vCPUs) than to match the spec of a Xeon processor.
But that's not how it works. He makes full use of EC2, there is a pain associated with moving. They estimate the pain and charge $1 dollar less.
Extracting the maximum that any company will pay for that service.
It's the old IBM mainframe model, do you think it makes sense for any company to use an IBM mainframe with less power than a normal server at a bucketload more cost? No, its the pain of switching that's expensive, so IBM milk as much as possible.
Newsflash! People applying non-cloud mindsets and methodology to cloud computing having trouble making sense of Amazon.
Seriously the CPU units are not a mystery, and plenty of people (myself included) have managed to do very successful capacity planning in AWS.
Make a cloud benchmark tool and run the same code on different instances....
MOPS and such.. Perhaps there is a need to implement a negligible cost measurement infrastructure providing some industry standard and normalized metering in those cloud instances.
I was considering using AWS... but it seemed to complicated with their calculator to get any kind of estimate of what it would cost me I went with dedicated servers instead.
Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
Big deal. Try asking azure support about licensing and they will flat out say I don't know. Assuming you bugged them at least a half a dozen times about the same questions beforehand.
> "A virtual CPU is whatever Amazon wants to offer in an instance series." No. The vCPU (Virtual CPU) aspect of an AWS EC2 Instance is the county of virtual cores that are exposed to an OS. In desktop computers, a quad core Intel CPU will appear to have four courses when looked at from inside the OS (my go-to way to count them in Linux is to run top and press 1). A quad core hyperthreaded Intel CPU will appear to have 8 cores. The vCPU metric simply tells you what the OS will show you, and tells you how many processor threads can run concurrently. > "If you deal with server sizing and instance price comparison, then the measure -- previously expressed as an EC2 Compute Unit or ECU -- is kaput." ... "It's the closest thing you'll find to an acknowledgement that ECUs are still in use behind the scenes, but Amazon no longer wishes to define them due to the changing nature of its underlying hardware."
Yes, ECU (Elastic Compute Unit) metrics are still used behind the scenes, but Amazon does publish them. Even for new Instances. Check out these URL's:
http://a0.awsstatic.com/pricin...
http://a0.awsstatic.com/pricin...
Of course, this isn't very parsable by human eyes. So someone started an open source project to display this data, and its available at http://www.ec2instances.info/
So yeah, TFA is wrong.
Amazon used to publish things in terms of ECUs and they switched to just telling you what the hardware actually is. I have no idea why that would not be considered an improvement. The article mostly complains about the t series being vague but that is no surprise - the t series has no fixed amount of cpu time. They have burstable cpu time that allows extra performance for short periods but a tiny amount of continuous cpu.
Back when Usenet was popular, members of certain groups in alt. used to call that kind of post a "spelling flame" or later a "spelling lame". If you want to complain about mbps vs. Mbps, please also have something helpful to say about the rest of the post.
How about OpenStack, which can be considered a bug-free cloud for a bug-ridden world?
1: Their code base is proven for production.
2: Their support for redundant VMs and moving them across clusters is top notch.
3: OpenStack works flawlessly out the box.
4: KeyStone authentication is bulletproof, beats IAM on every front.
5: OpenStack offers two ways to store data -- Swift for objects, Cinder for block-level I/O.
If OpenStack wasn't going to crush AWS in the next year or two, IBM, HP, and RackSpace wouldn't be betting the farm on this.
The old VAXen that DEC sold came with a measure called VAX Units of Performance (VUP's). You bought stuff with a certain amount of VUP's rather than raw performance specs. Now Amazon is selling some Amazon-specific measure of performance that benefits them more than us. More signs the cloud is just re-inventing the mainframes and minicomputers of old. Cheaper, faster, more flexible, and so on for sure. Same concepts, though, plus what it seems is the same bullshit. :)
Maybe its all meant to be like mobile phone plans. So complicated that no one can workout which better or cheaper