>It seems to me that, by default, what we'd want is a sync api which
under the hood, creates one task per drive accessed, or maybe
max(drives_in_use, number_of_cores). I think the OS will make them
async with the drive hardware anyway, though, so number_of_cores doesn't
matter.
I don't think drive access is the issue; but 50k network clients is
nothing unusual as a target for a concentrator process that's handling
fan-out for a service that is being accessed by (say) engines in a large
grid, or connected client applications - and if you have a target user
community that might connect its a darn site easier to design for that
than to scale horizontally (until you absolutely have to, anyway).
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
