News for hackers. Stuff that matters.
Re:Improving Kubernetes Scheduler Performance by smoyer on Wednesday February 24, 2016 @08:58AM (#11166722)
They also removed two rate-limiters that someone had (presumably intentionally) put into the code. You always have to wonder when you see "protective code" like that - why was it added in the first place? Was it premature optimization? A guess? Often if a weak component is strengthened, you end up with "forgotten" code like this and it's always an effort to find and remove it.
Re:Improving Kubernetes Scheduler Performance by hongchaodeng on Wednesday February 24, 2016 @01:05PM (#11168780)
Unleashing rate limiters is like releasing a water gate -- now you know which part is too weak to stop the flood.

By doing this, we can have more insights of system performance and find out which part is too "weak".

There is no reason that we couldn't increase the rate limiter if we keep improving the system in overall.