3 ms·
Ok!, the two instances you were seeing were duplicate listings of the same instance. That bug was introduced a few days ago by some database optimizations, and
by adamsmith 14y ago
Ok!, the two instances you were seeing were duplicate listings of the same instance. That bug was introduced a few days ago by some database optimizations, and is now fixed! Thanks for reporting it.
The 1.56 core-hours is mostly from inst_KGN6tZdFgoeL2C9KPKBsNA which has four physical cpus and has been running for almost an hour at this point.
Thanks so much for trying this out!!!
- panarky 14y agoIt shouldn't matter how many physical CPUs there are, I only care how many my VM can use and how fast each one is. If `cat /proc/cpuinfo` or `top` only shows one CPU, I wouldn't expect to be charged for 4 of them.
- adamsmith 14y agoYou are of course absolutely right! There was a bug (now fixed) that was causing only one cpu to show up in the VMs. All instances started after now should have the proper number of cpus visible. (Note, the number of cpus might be higher than the number of physical cpus if the host cpu supports hyperthreading.)