talks   10422

« earlier    

Екатерина: _niece
Всех нас губит нас, товарищи, внешний локус контроля: не о том надо думать, что в голове у вам незнакомых и едва ли существующих людей, а о том, что вам нужно. Прямо так просыпайтесь утром и спрашивайте себя - только не "чего я хочу?", а то пойдет счастье для всех и прочая удешевленная философия - а "чего мне надо?". С ответа на этот роковой вопрос начинается гражданское самосознание. Второй вопрос: как этого добиться и где слабые места у того, кто мешает получить или может дать и не дает. С этого уже начинается политическое мышление.
psychology  russian  politics  protest  talks  mots 
10 days ago by some_hren
"Stop Rate Limiting! Capacity Management Done Right" by Jon Moore - YouTube
How to apply backpressure to clients using an Additive Increase/Multiplicative Decrease scheme (like with TCP) based on the number of concurrent connections. Rate-limiting sucks because if the service isn't healthy connections build up on the proxies and the service stays overloaded. Backpressure needs to be propagated throughout the request path.

In the demo, multiple proxies to an app server start with a low limit for concurrent connections that slowly increases as OKs are returned by the app server. When the app server applies backpressure to a proxy it decreases the limit by 25% and rejects connections until the number of concurrent ones is under the limit. The sum of the concurrency limits for the proxies ends up hovering around the actual capacity of the app server, without any extra communication between the proxies or app server, and without any hardcoded limits on the proxies. Also, when the service is at full capacity the number of concurrent connections at the proxies can be predicted by Little's Law, NumConcurrent = ArrivalRate * Latency (on average), if the capacity (NumConcurrent) of the service is known.

It seems like app servers could also use AIMD to choose when to apply backpressure, decreasing the concurrency limit when average latency or something crosses some threshold.
videos  queues  scale  youtube  talks  distributed  StrangeLoop  JonMoore  via:torbiak 
13 days ago by campbellr
Every JavaScript framework tutorial written more than 5 minutes ago
Step one, the tutorial said, was to install Tupress. Well, duh. Then Roger had to install Bistup — a lightweight wrapper, whatever that meant. After that, he had to install Claster, which provided a thin unopinionated layer of utility methods and middleware. He didn’t know what that meant either, but installed it anyway.
debugging  framework  javascript  tutorials  humor  talks 
13 days ago by ntschutta

« earlier