from Hacker News

Mfio – Completion I/O for Rust

by wspeirs on 12/15/23, 6:06 PM with 13 comments

• by bjfish on 12/15/23, 7:45 PM

  The log scale charts make it seem like the performance is all the same. It would be nice to see relative performance in a table or chart.

• by lokeg on 12/15/23, 7:42 PM

  Skimming this I did not really understand the programming model difference from glommio or tokio-uring. Aside from striving to be cross-platform, how is this significantly different?

• by atlas_hugged on 12/16/23, 1:55 AM

  Never heard of this “coloring” thing.

  From a quick google it’s about the “color” of a function being red or blue as defined here (I think): https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...

  Isn’t this weird and unnecessary? I dunno. It’s probably just me.

• by KolmogorovComp on 12/15/23, 8:11 PM

  The associated video has quite a cool intro [0], however after that it’s fairly slow and lack details, apart from perf and cross platform characteristics (which are cool).

  [0]: https://www.youtube.com/watch?v=EBAC1KcjR28

• by spullara on 12/15/23, 8:53 PM

  I've always wondered why completion i/o systems require you to hand them a buffer rather than a buffer pool. Handing them a buffer means that you are keeping a huge amount of memory allocated when you have a huge number of connections.