Hacker News new | past | comments | ask | show | jobs | submit login

And how is that different from worse latency due to cpu throttling from your users’ perspective?



this is a predictable worse latency due to CPU throttling, i.e nothing is suddenly introduced in the system. but the other case is worse i.e a non critical microservice can cause outage on your critical microservice.

imagine some non critical system like blog-service suddenly causing 2-3% new order creation failures


Fixed queue, so it'll only take as many as it can process and reject the rest, which can be used to do scaling, if you have a cluster. With shares it would think it has all the CPU cores available and oversize the queue.


Doesn’t answer my q really. At least in kubernetes scaling is done by measuring usage against the request (shares) not the limit (quota)




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: