Re:AWS Fargate – Run Containers Without Managing Infrastructure
by eropple on Wednesday November 29, 2017 @02:11PM
(#15809807)
Most web apps are IO bound, not CPU bound, and a throttled T2 has IO to spare versus its CPU usage.
[ Parent
| on HN ]
Re:AWS Fargate – Run Containers Without Managing Infrastructure
by Johnny555 on Wednesday November 29, 2017 @02:17PM
(#15809886)
t2's are great until something happens and you really need the full CPU, then you get throttled and suddenly your service goes down because it can't keep up with the load.
If you use t2's for anything important, keep an eye on the CPU credit balance.
Re:AWS Fargate – Run Containers Without Managing Infrastructure
by blasdel on Wednesday November 29, 2017 @08:03PM
(#15812461)
I work on T2, and boy do I have a fix for you!: https://aws.amazon.com/blogs/aws/new-t2-unlimited-going-beyo...
Re:AWS Fargate – Run Containers Without Managing Infrastructure
by cjsuk on Wednesday November 29, 2017 @02:59PM
(#15810297)
Just applying selinux policy on CentOS 7 will kill the CPU credits on a micro instance. Running updates is a risky businesss.
Re:AWS Fargate – Run Containers Without Managing Infrastructure
by ryeguy on Wednesday November 29, 2017 @04:27PM
(#15811017)
But if you get throttled in the first place that means you're going to have some kind of performance degradation since your server was using more than the baseline level. Web apps being IO bound isn't relevant here, because the only requirement for issues to arise is for your server to have consistent 20%+ cpu usage.
Re:AWS Fargate – Run Containers Without Managing Infrastructure
by jrochkind1 on Wednesday November 29, 2017 @05:09PM
(#15811357)
Well, they're relevant in that a heavily IO bound app is probably unlikely to use much CPU -- it's too busy waiting on IO to use 90% of CPU, and maybe does stay mostly under 20%. Obviously this depends on a lot of details beyond "IO-bound", but it is not implausible, and I think does accurately describe many rails apps.