Erlang / Erlang Advanced Interview questions
Why should high-priority processes be used sparingly in Erlang?
Erlang's whole scheduling model assumes most processes are roughly equal citizens sharing time fairly via
reduction counting. Marking a process high or max priority breaks that assumption
locally: it can consistently jump ahead of normal-priority work on the same scheduler, and if it runs
frequently or for long stretches, it can starve normal-priority processes of scheduling time, even though
they're otherwise ready to run.
In practice, very few application-level processes actually need this — genuine latency requirements are usually better solved by architecture (dedicating a process to just that fast path, using dirty schedulers correctly for native work, or reducing message queue depth) rather than by escalating priority. Overusing elevated priorities tends to create hard-to-diagnose "why is everything else sluggish" issues, since the starved processes show no error, just quietly reduced throughput.
Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!
Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.
Invest now!!! Get Free equity stock (US, UK only)!
Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.
The Robinhood app makes it easy to trade stocks, crypto and more.
Webull! Receive free stock by signing up using the link: Webull signup.
More Related questions...
