11–14 of 14 posts
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.
yeah that's the most honest charting I've seen. they're not looking for headlines, respect
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.
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.
I think it just happens to be that we like assigning colors to differentiate things in the mathematical side of CS.
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.
For TCP, you'd generally want to have a buffer pool and issue one repeating request that takes buffers out from that pool. This is what io_uring allows you to do. The difficulty comes from APIs ability to expose that buffer pool nicely. I am on the lookout to model this better, but no clear solution that does not make assumptions about the backend at play. For now, however, with careful design you can skip the alloca…