2 ms·
There’s no network latency involved as it’s an in memory, embedded database. Also, max throughput here is ultimately a sum of how fast the memory allocator is
by Eikon 7y ago
There’s no network latency involved as it’s an in memory, embedded database.
Also, max throughput here is ultimately a sum of how fast the memory allocator is and memory bandwidth which, even with a poor implementation would be orders of magnitude more than what you can do with standard NICs and Linux kernel networking stack.
Moreover, as a consequence, far less context switching is involved.
- Znafon 7y agoI thought it was possible to embed Redis.
- Eikon 7y agoPossible don’t mean ubiquitous. You get no support and plenty headaches when you start to do that sort of weird, unsupported things with a product.
- shepardrtc 7y agoAhh I missed the part about the network. That makes much more sense, then.
- Exuma 7y agoCan you explain why redis require extra network time?
- shepardrtc 7y agoIts just time to transfer across the network, whereas this project is in-memory with the program that's calling it.
- stevekemp 7y agoThey do discount networked solutions, but then talk about making HTTP-calls with JSON payloads. Or was that just for testing?