Please sign in to comment.
Meter calling accept(2) with available pool capacity (#1278)
* Meter calling accept(2) with available pool capacity Talking through this with Nate and Richard, we realized that accepting new clients without taking account for the available capacity of the thread pool doesn't improve throughput, it only hurts it in the case of multiple workers. If a worker pauses (or starts up before other workers), then a worker can accidentally suck up a high number of clients and leave unused capacity inside the other workers. This change will smooth out this issue, with a minor penalty to maximum throughput. * Rewrite the conditional to be less confusing
- Loading branch information...
Showing with 10 additions and 2 deletions.