report bogomips with the rest of cpu info

[joewilliams]

Add bogomips to the cpuinfo output.

[SuperQ]

This needs a DCO sign-off. You can use git commit -s --amend to add it.

[SuperQ]

Thinking about this, I'm not sure what use this is. Bogomips is not really a useful metric nor useful for inventory.

Any specific reason why this should be included?

[joewilliams]

@SuperQ we would like to use it as an agnostic "size" of a server. For instance, a server with higher cores * bogomips probably has a bigger compute capacity than a smaller one regardless of CPU vendor, generation, etc.

[SuperQ]

This will not be helpful for your use case. You can not use label values in queries that way, they are treated as opaque string values.

I also don't think you're going to get the value out of bogomips that you think you will. Here's a simple example.

• My laptop: 13th gen i7-1365U
• My old VPS host: Xeon E-2236

CPU benchmark comparison shows that the Xeon is about 5-6% slower than my laptop. Although, I'm not sure if that benchmark site results include P and E cores correctly.

But from a bogomips perspective, it says the Xeon is 6799.81, and the laptop is 5376.00. And that still doesn't take into account P and E cores as it shows them to be the same.

I highly suggest you don't use bogomips for any kind of comparisons. They haven't really been useful for 20 years, since the introduction of cpu frequency scaling and hyperthreading.

[joewilliams]

Thanks for the info!