11 ms·
I am consistently surprised how many VM hosts refuse to tell you what your CPU guarantees are. EC2 at least gives you a general equivalence to a specific hardwa
by MichaelGG 14y ago
I am consistently surprised how many VM hosts refuse to tell you what your CPU guarantees are. EC2 at least gives you a general equivalence to a specific hardware. Rackspace refuses to go into detail. Others I've spoken to will only commit to saying "core", without specifying what the reference hardware is. And even then, actually making sure you've got a commit of that CPU is a whole other issue. I think EC2's compute units are a commit, though.
Linode's "priority" seems like ex-Slicehost's way of saying "hey bigger machines get a higher proportion"... nothing really useful for figuring out exactly what you're buying.
And you can't ever really figure out what you have: things could be severely over-committed, and you'll never know until you get starved. So you can't just benchmark your way out of it.
- spindritf 14y ago> Others I've spoken to will only commit to saying "core", without specifying what the reference hardware is. There's probably no reference hardware beyond `cat /proc/cpuinfo`.
- patrickgzill 14y agoEven that is not accurate... on an OpenVZ instance set for 2 cores, this command gives me the specs on the CPU, an E5405, twice. Of course, this chip actually has 4 cores, so to show only 2 is not really accurate. On a nearly-identical XenServer instance, it shows the same info, showing 2 CPUs but identifying the CPU as a 6-core Opteron. From this, however, you cannot infer what percentage of those 2 virtual CPUs that you are going to get.
- deleted 14y ago[deleted]
- pixie_ 14y ago/proc/cpuinfo for me shows 4 Intel Xeon L5520 @ 2.27GHz
- martinp 14y agoMy Linode also shows 4 L5520, but that's probably 2 cores with 4 threads as the L5520 [1] has 4 cores and 8 threads in total. http://ark.intel.com/products/40201/Intel-Xeon-Processor-L5520-8M-Cache-2_26-GHz-5_86-GTs-Intel-QPI http://ark.intel.com/products/40201/Intel-Xeon-Processor-L55...
- astrodust 14y agoI used Slicehost and Linode in parallel until it was obvious that Linode's CPU performance was quite consistent and Slicehost's would waver from marginally better to significantly worse. This is probably because Linode is configured to use a fixed CPU time allocation method. Amazon's CPU commitments are just as reliable as Linode's, but they seem to be less for the same dollar. As for actual hardware, to go based on `/proc/cpuinfo`, some of the older instances I manage show up as Xeon L5420 CPUs at 2.5GHz, and the newer ones tend to be L5520 at 2.27GHz for what that's worth. They seem fairly consistent, and if you don't like what you get, just like AWS you can delete the instance and get a new one. You get refunded for your unused time.
- maushu 14y agoYou get refunded for your unused time. Please notice that the minimum time block is a day. If you spin an instance, you pay for the whole day.
- seats 14y agoI cofounded slicehost and spent a lot of time at Rackspace thinking about this exact problem relative to Rackspace Cloud Servers. The real issue is hardware skew. We like to buy/sell and build on cloud as if it is a pure utility where every unit is equivalent, but every year processors change, go EOL, etc. As a provider you have to make a call about how much of that complexity you expose to the end customer. Some customers want complete transparency, which I understand, but the downside of that is hundreds of variations of pricing options and complications around managing heterogeneity (e.g. how do you represent simply how much available capacity there is when you effectively have 300 variations of the same 'size' instance). Of all the component parts of compute, CPU is the one that changes the quickest. Disk capacity is easy to model, disk throughput has changed much at all (minus the introduction of SSD), memory is pretty stable (minus some increases in databus rates). All in for the typical instance in a multi-tenant virtual environment, the same today as in 2006, the two most vaguely defined attributes are cpu and i/o. With the increasing use of 10gigE as well as SSD, hopefully we finally push through the i/o piece. Not sure what it will take to get us there for a clean way to model and describe 'standard cpu' as a provider. Also, if anyone has specific questions about Slicehost cpu priority handling circa 2006-2008 or Rackspace Cloud Servers cpu pre OpenStack, just ask and I'll be happy to answer.
- MichaelGG 14y agoCreate some sort of composite performance profile, then give me CPU information in terms of that. EC2 sorta does this[1], and although it's far from precise, at least it gives us a rough guideline and is at least an actual statement on what we're going to get. The other issue, which I don't see Rackspace (or Slicehost or many others) addressing is the actual commit. It's fine to say "you get 2 cores", but then not tell me if those are reserved or if they might be sometimes overcommitted. This is a larger issue, because it means things might work fine... until they don't. (I tried one provider out, and things worked swell in all our tests, but rarely in production, the entire VM would get paused for a few hundred ms ore more; something that wouldn't happen if there was a non-over-commitment guarantee. Right?) 1: "One EC2 Compute Unit provides the equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor."
- 14y ago