It would still saturate I/O throughput of nodes configured in less than optimal way. We’ve got quite a lot of improvements since then, for example the hashtable-based storage.
Hashtable was explicitly implemented for the select network. Guess why? Remember the customer with supposedly such a high I/O needs that we had that joyful summer last year? Remember that they ended up choosing the select network instead? My hypothesis is that the select network also underperformed, and so some way to speed it up had to be implemented on top of whatever optimizations were implemented on the community network.