> weight wi is calculated as qi/ui, where qi and ui represent the recent query-per-second (QPS) rate and CPU utilization of replica i.
The pathological case describes a situation where antagonist loads are soaking up CPU on some on the machines, but WRR equally distributes the load because weight formula prioritizes the utilization of the individual tenant, not of the entire machine. Wouldn't including the the machine utilization (probably downweighted) into the WRR formula also solve the issue?
We have gone from nearly 500 employees worldwide at December 31st to 12 full-time and part-time employees, including some temporary or contract employees. We are no longer liable for any of our old leases, including our former corporate headquarters in San Francisco."
Generally, that seems valid to me.
Basically a leaky abstraction, you have to think whether your code will block or not.
Go went through the same process, before eventually figuring out that they do need to make their lightweight threads (goroutines) preemptive.