3 ms·
Always found ec2instances.info super useful. But found vCPU such a weird unit (that's on AWS of course), as it changes with every CPU generation. So I bought cl
by nielsole 6y ago
Always found ec2instances.info super useful. But found vCPU such a weird unit (that's on AWS of course), as it changes with every CPU generation. So I bought cloudinstances.info. Originally wanted to demystify the vCPU. Never got around to actually building it.
Anything you would like to see?
Was thinking of the following:
- some stock synthetic benchmark
- response times of "todolist" app in django, express, ... for real-world data
- all kinds of io latencies and percentiles
- detailed CPU info including cache sizes (and maybe even cache thrashing of noisy neighbours as probably not everyone uses cache allocation technology yet)
- comparing with some dedicated hardware (would be interesting how nitro compares to kvm based cloud providers)
Any more ideas?
- wmf 6y agovCPUs are just hardware threads (or "cpus" in Linux) which also change every generation; it has never been intended to be a measure of performance.
- GrantZvolsky 6y agoI remember raising an issue[1] back in 2015 asking for the unit to be changed from `cores` to `vCPUs`. Small world. [1]: https://github.com/powdahound/ec2instances.info/issues/111 https://github.com/powdahound/ec2instances.info/issues/111