This paper shows that in single-threaded writes to Redis, the kernel IO mediation takes 84% of processing time. https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-peter_simon.pdf …
-
-
Replying to @hausdorff_space
For single-threaded reads, it's ~62% of the time. In both cases, ~70% of time in the kernel is spent in just the networking part.
1 reply 0 retweets 0 likes -
Replying to @hausdorff_space
They argue hardware provides most of things you want the OS to do anyway, so they yank the IO stack and configure hardware themselves.
1 reply 0 retweets 0 likes -
Replying to @hausdorff_space
e.g., they set up the virtual network cards to do multiplexing, which makes the multiplexing 0-copy, since the kernel normally copies it.
1 reply 0 retweets 0 likes -
Replying to @hausdorff_space
I wonder why they didn't just go with RDMA. It seems like a natural fit and requires less hardware-specific config. Is it security issues?
2 replies 0 retweets 0 likes -
Replying to @hausdorff_space
@hausdorff_space In case you haven't seen it, they mention a reason just before section 3. Their reason implies they didn't want to virt...1 reply 1 retweet 0 likes -
Replying to @danluu
@hausdorff_space ...ualize RDMA channels and mux multiple virtual queue pairs over the same QP, which is reasonable but causes you to run...1 reply 1 retweet 0 likes
@hausdorff_space out of the number of QPs the NIC will handle on the fast path quickly, even if you're only talking to a few machines.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.