3 ms·
Network I/O is almost always the slowest part of any application regardless of the protocol and data encoding mechanism. It seems to reason that if you can co-
by CharlieDigital 3y ago
Network I/O is almost always the slowest part of any application regardless of the protocol and data encoding mechanism.
It seems to reason that if you can co-locate your calls into a single process, you'd gain at least 9x.
- sgt101 3y agoYeah - I think that their argument would be that their approach enables you to do that, and that there are significant gains on the table without that last step. My main critique is that it's one example, and it would be good to see the technique exercised across a number so that we can see the strengths and weaknesses.
- bob1029 3y agoFor same process + core + hot cache & pipeline, your upper bound is something like 1,000,000x faster than a trip within the same datacenter. This intuition is what encouraged us to run with SQLite in production back when most developers didn't think it was a good idea.