4 ms·
This seems like a useful practice. Do you log how often this happens and which task is the winner? It seems like without that, you may not notice actual issues.
by pspeter3 9y ago
This seems like a useful practice. Do you log how often this happens and which task is the winner? It seems like without that, you may not notice actual issues.
- KirinDave 9y agoSince the tasks are identical, the only real value such a metric would have is in considering memory allocation for green threads and other issues around memory pressure and resource pooling. Usually, it doesn't matter why the consumer finds it slow; it could be anything from an unusual I/O issue (AWS is notorious for brief but painful networking issues) to a VM peer suddenly becoming ill behaved before being throttled.
- dswalter 9y agoIs your list of things AWS is notorious for available on your blog somewhere? That's valuable information.
- KirinDave 9y agoAWS is notorious for having absolutely awful networking. Every other CSP rep rightly digs on them. They're also notorious becuass ECS is SO BAD.
- Scramblejams 9y agoIn your experience, who’s got the best networking?
- esrauch 9y agoIf you find that something shifts and you are almost always starting the second task but the first task is still winning then you are in a state where the solution became extra load for no benefit.