CPU Steal & the new Linodes

Just want to say at the outset that I/we are extremely happy with the new SSD-backed 64bit servers and their performance. The upgrades came just in time (really, another ten days and it would have been too late!) to stop us migrating away after 3 years on Linode. We have upgraded our most performance-critical Linodes and the improvements are clear and very satisfying.

This post is just to note some oddness with CPU steal … going beyond the discussion in the comments to the blog post that announced the new SSD-backed product range.

In short, where before we had CPU steal, now we have almost nothing recorded as CPU steal but the total amount of CPU recorded no longer adds up to a multiple of 100%. So instead of CPU steal we have missing CPU :o

The old 32-bit Linode (7 days - check out the CPU steal):

~~![](<URL url=)https://s3-eu-west-1.amazonaws.com/lmax … ore-7d.png">https://s3-eu-west-1.amazonaws.com/lmax-static/images/before-7d.png" />

The new 64-bit Linode (24h since the migration: notice CPU no longer adds up to a multiple of 100%):

~~![](<URL url=)https://s3-eu-west-1.amazonaws.com/lmax … er-24h.png">https://s3-eu-west-1.amazonaws.com/lmax-static/images/after-24h.png" />

Overall we're happy but {i} this does seem odd and {ii} it would be interesting to know if anyone else is seeing this.~~~~

2 Replies

I've noticed total cpu does not add up anymore in munin even on actual hardware either. I suspect something something kernel changed recently, and munin is missing some new metric.

This is the current "worst case" I could find on my Linodes. Not much to brag about :)

Performance is stellar, no complaints.

![](" />

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct