Comment by dcrazy

19 days ago

The Apple software stack makes heavy use of thread pools via libdispatch. Individual work items are tagged with QoS, which influences which thread picks up the work item from the queue.

There's also priority inheritance (two different systems for it) so that requests originating from users/apps are more important.

Swift concurrency is more about structured concurrency than thread pools. A lot of other systems seem to use futures, which aren't good at priority inheritance.