@ben_lubar That's... more subtle than I was expecting; we're mostly under the 24-credit mark on the left (if only just), and mostly at/over on the right. Not the smoking gun I was hoping for, though, in terms of pining down a specific event.
@e4tmyl33t said in AWS issues:
I don't think that's how it works. You only earn credits if you're idle, not if it's under any sort of load. While you're burning credits, you don't earn any. At least that's how I read it.
It does; our credits accumulate regardless of usage, they are just spent immediately if we're using the CPU above the threshold.
AWS said in [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-instances.html#t2-instances-cpu-credits]
Each T2 instance starts with a healthy initial CPU credit balance and then continuously (at a millisecond-level resolution) receives a set rate of CPU credits per hour, depending on instance size. The accounting process for whether credits are accumulated or spent also happens at a millisecond-level resolution, so you don't have to worry about overspending CPU credits; a short burst of CPU takes a small fraction of a CPU credit.
When a T2 instance uses fewer CPU resources than its base performance level allows (such as when it is idle), the unused CPU credits (or the difference between what was earned and what was spent) are stored in the credit balance for up to 24 hours, building CPU credits for bursting.
So, maybe we should talk short- and long- term fixes. @apapadimoulis, would you approve upgrading the instance class to t2.large to accommodate our current credit usage, until the forum can be moved out of AWS in December? If you wanted to crowd-fund the difference, I'm sure enough people (myself and @accalia at least) would donate.