4 ms·
Excluding t1.micro instances you are getting a fixed, dedicated amount of CPU per instance, CPU is not a shared resource on EC2.
by shrike 14y ago
Excluding t1.micro instances you are getting a fixed, dedicated amount of CPU per instance, CPU is not a shared resource on EC2.
- bradleyjg 14y agoSo just to be clear: If I have a reserved instance I'm not using there is a CPU sitting somewhere doing running HLT cycles? Wow.
- toomuchtodo 14y agoVs needing CPU cycles and you having to wait if someone else is using that shared CPU time? There are always tradeoffs.
- bradleyjg 14y agoI didn't mean to be critical, customers certainly get better latancy on a fixed time slot implementation over an interrupt based QoS system. I'm surprised from Amazon's perspective, especially because they are competitive on price.
- shrike 14y agoIf you have a reserved instance that is in the running state but you aren't using it, then yes. If you have a reserved instance that isn't running then that slot is likely available on the spot market.
- Negitivefrags 14y agoWhy is it that you get such variable CPU performance on different instances of the same type then? I was using a whole bunch of c1.medium instances and found the CPU performance varied by a factor of at least 2.
- benologist 14y agoCould that be because of old vs new hardware?