Admission control can be more effective when it directly controls concurrency when possible (e.g. at server level), rather than request rate, because excess concurrency->bottleneck resource saturation->throughput collapse. Related DB paper: https://t.co/PKwLcz0Y7z

@pkhuong Thanks for reminding me of that paper. In my case I have completely reliable failure detection, so that’s not a rationale for nonblocking CM. In any case, directly controlling concurrency is likely more effective than backoff: https://t.co/PKwLcz0Y7z

Sometimes I come across a paper that would never be accepted at a top conference but is exactly what I need for my current problem. This one addresses retry + backoff in the context of OCC and finds that directly controlling concurrency is more effective: https://t.co/PKwLcz0Y7z