I like to say that the BEAM's preemptive scheduling provides non-blocking IO AND non-blocking computation. To expand on your workload description: things like

I like to say that the BEAM's preemptive scheduling provides non-blocking IO AND non-blocking computation. To expand on your workload description: things like waiting for a database query or an API result are smoothly handled in this paradigm; the process goes to sleep for a bit whle another request is processed. If your workflow is like a delivery truck which makes a lot of stops, "faster trucks" doesn't help much with throughput. "More trucks" is better.