4 ms·
The latency isn't from the cipher; it's from touching the data an additional time. A NIC with inline encryption adds negligible latency but Google probably does
by wmf 9y ago
The latency isn't from the cipher; it's from touching the data an additional time. A NIC with inline encryption adds negligible latency but Google probably doesn't have those.
- dward 9y agoIf anyone were to have those, it would be google.
- wmf 9y agoSince they design their own NIC, Google certainly has the capability to include whatever features they want. Yet Andromeda appears to be implemented in software.
- theptip 9y agoThe problem is that Google (and all other large cloud providers) use an SDN, and so you can't just encrypt traffic at the NIC level -- you need to just encrypt the encapsulated overlay traffic, while leaving the underlay unencrypted (so that intermediate nodes can route the overlay network traffic). There are a number of technologies that support this kind of thing at the kernel level, but 1) layering these onto an existing SDN is not trivial, and 2) the extra encoding/decoding will absolutely have a performance impact if you're trying to do it at line rate on a 10Gb NIC, e.g. see https://www.weave.works/blog/weave-net-performance-fast-datapath/ https://www.weave.works/blog/weave-net-performance-fast-data....