15 ms·
Datacenter RPCs can be general and fast
- baybal2 8y agoBeen working on something similar as a sub-sub-sub contractor for Alibaba's DCs. The physical latency is nowhere near as scary as latency of a shitty NIC and software... 20 metre roundtrip is only 200 nanoseconds, or about the same as pulling something from DRAM.
- CoolGuySteve 8y agoThe Linux network stack needs to get its shit in order. Kernel bypass libraries like EVFI transmit UDP in 250ns whereas the kernel typically takes several usec. Transitioning into kernel space shouldn’t take that long so a lot of needless instructions must be getting executed.
- baybal2 8y agoLinux net stack is tooo fat, and have to support a gazillion features that are only needed by less than 10 companies in the world each. That's lack of leadership for you... Kernel people should be pushing back more on such features
- syn0byte 8y agoWhy would they stop companies from contributing optional code to Linux for their products when you can just (not) compile what you want of it? The linux eco-system does not begin and end with a RHEL/Ubuntu binary distribution built to run on every crappy PC in the last decade.
- baybal2 8y ago1. not all minority feature commits are config disableable 2. focus - kernel keeps accumulating abandonware code for gimmick features/drivers
- ignoramous 8y agoFor any meaningful elastic deployment at scale, Linux's (or rather any OS) TCP/IP stack will have to be bypassed through user-space programs: It has all of the upsides and few of the downsides. Ref: https://opennetworking.org https://opennetworking.org Not just the datacenters, but even 5G deployments, which would be exclusively IPv6 based, would sport user-space processing of packets and flows. Ref: https://opencord.org https://opencord.org
- CoolGuySteve 8y agoExactly my point, the kernel shouldn’t have to be bypassed. It should just be fast.
- ignoramous 8y ago(not an expert, just someone keeping abreast with development in the networking world) There are inherent problems with relying on the OS in an elastic environment. Kernel's TCP/IP stack could be made to expose very specific APIs to help with NetworkFunctionVirtualization (NFV) and Software-defined Networking (SDN), but the advantages are not clear: 1. Vendors to rely on Kernel devs to do the their biding for their NFV/SDN deployments, and wrestle with various other priorities Kernel might already have. 2. Build/deploy the updated Kernel fleet wide, with those changes (which now include other Kernel changes vendor may or may not want). 3. Cater to strict Kernel community guidelines and expect to be driven by the established processes governed by designated gatekeepers, costing vendors time and speed to market. With a userspace solution, esp since it allows vendors to be performant by simply interfacing with NICs, the vendors have a measure of control on their own destiny: 1. Deploy at will, at pace. 2. Ability to do custom packet/flow (virtualization), on-the-fly (SDN) even, without requiring any assistance from any other part of the system not in their control. 3. Reduce external factors that might influence their timelines or priorities. The generic problem, however, with the Kernel's TCP/IP stack needing improvement is orthogonal to this. That effort will have little to no bearing on the direction the Networking industry is moving, imo. --- Google Maglev (network load balancer): https://ai.google/research/pubs/pub44824 https://ai.google/research/pubs/pub44824 Dropbox MagicPocket (bypassing OS' VirtualFileSystem for storage at scale): https://blogs.dropbox.com/tech/2016/05/inside-the-magic-pocket/ https://blogs.dropbox.com/tech/2016/05/inside-the-magic-pock... Facebook Haystack (an example of problems working with VFS at scale and a solution to it): https://code.fb.com/core-data/needle-in-a-haystack-efficient-storage-of-billions-of-photos/ https://code.fb.com/core-data/needle-in-a-haystack-efficient... NFV: https://www.electronics-notes.com/articles/connectivity/nfv-network-functions-virtualisation/what-is-nfv-basics.php https://www.electronics-notes.com/articles/connectivity/nfv-... VNF: https://www.electronics-notes.com/articles/connectivity/nfv-network-functions-virtualisation/virtualized-network-functions-vnf.php https://www.electronics-notes.com/articles/connectivity/nfv-...
- justicezyx 8y agoNice, although they need to went into production to prove any worth. This type of innovation is pretty much appeared on a daily basis in every senior engineer's head. Not dismissing, it's just a matter of fact in real world systems.
- zrb 8y agoBut where is the RPC? This just seems like messaging EDIT: Found this... https://github.com/erpc-io/eRPC https://github.com/erpc-io/eRPC
- deleted 8y ago[deleted]
- deleted 8y ago[deleted]
- peterwwillis 8y agoAm I missing something, or is this post effectively saying all you need is a perfect network and suddenly ethernet is fast?
- shereadsthenews 8y agoThe more interesting thing in this paper is the gulf between state of the art and mainstream practice. Most of you people are happy getting ~100K QPS in a 32-core box and this guy is getting 10M QPS per core.
- diffserv 8y agoThat is hardly the state of the art: they are basically sacrificing all abstractions that are rightly so required in the name of speed. This is no different than using vanilla DPDK with no congestion and flow control and being able to process 20 mil packets per core (better than the numbers in the paper). Getting 75Gbps per core using RDMA is hardly hard or new. You can't use this abstraction for anything ... really unless you are on a completely lossless fabric that has enough capacity to avoid congestion. Yes, Google/MS/FB are going towards such fabrics but the hard part is not building the RPC abstraction suggested in this paper---the hard part is getting to that fabric. Just to put things into perspective, if you had a quantum computer you could do all sort of crazy stuff with it. You could "parallelize loops! and be super fast" is what this paper is suggesting (I specifically chose parallelizing loops cause there is nothing new in it).
- shereadsthenews 8y agoWell this sets a lower bound on the state of the art that is in any case orders of magnitude higher than what many people suffer from in industry practice.
- diffserv 8y agoJust to restate what I said---you cannot use this in its current state in production (or industry), ever. And by the time it becomes useful, it becomes a natural solution because the infrastructure supports it. Every person that works on kernel knows the overhead that comes with abstractions. Everybody that has worked with DPDK knows that you can get 20Mpps+ on a single core. All they have done is to "frame" the usage and the term RPC differently ... i.e., it's all story telling and no real meat :) Look at the previous set of publications by the same author: e.g., Achieve a Billion Requests Per Second Throughput on a Single Key-Value Store Server Platform, etc. they are all based on a single assumption that if you don't implement X and Y in your stack you can get better performance. Of course, you can. If you use your calculator to only compute 2+2 you might as well hardcode 4 as the output of your calculator. They are not setting a lower bound. They are hardcoding and bypassing the parts they don't find useful.