right, that was around the time that everyone using the BSD network stack became a thing. Did you mean to say thrashy (not that it's wasn't also trashy)? Beca

right, that was around the time that everyone using the BSD network stack became a thing. Did you mean to say thrashy (not that it's wasn't also trashy)? Because IIRC that was the main problem. There were issues with, for example, the memory mapped area leaving the caches of the resident core that the process lived on; and also generally BeOS was terrible at pinning processes to CPU cores. And I recall that the sentiment was also that the network stack needed low latency in general and that it was rather difficult to get a good implementation of a userland network for these reasons. I imagine that at least some of these concerns may play out in more contemporary userland network stacks. Possibly, worse so if you don't know what is going on with noisy neighbors in containerized or even vm-ized deployments (though I would guess that Amazon/GCP but maybe not Azure does a good job of quotaing/throttling vms)