5 ms·
We use it at Netflix for our Open Connect CDN. In general, the FreeBSD performance is far better for our workload (we have served up to 100Gb/s from a single-
by drewg123 9y ago
We use it at Netflix for our Open Connect CDN.
In general, the FreeBSD performance is far better for our workload (we have served up to 100Gb/s from a single-socket CDN node). In fact, I'm sitting here reading HN while watching a single-socket E5-2697A machine ramp up past 92Gb/s for a 100% TLS workload.
- 2trill2spill 9y agoI hate to nag you. But whats the status of TLS sendfile? That feature is a great example of what FreeBSD can do, unfortunately it's still closed source.
- drewg123 9y agoYes, sorry. We keep getting busy doing other things. I'm actually working on getting it upstream now. I was testing some "before upstreaming" cleanups to make sure I didn't break anything :)
- geofft 9y agoCan I ask you what your network hardware is and how customized your kernel is (i.e., are you patching the network stack at all or running some vendor-customized drivers, or is it all in mainline)?
- drewg123 9y agoWe use fairly standard Mellanox and Chelsio 100GbE NICs. Except for TLS sendfile and our vectorized mbufs, most of the patches that we've been running have actually been to the VM system. Thankfully, due in large part to the recent efforts to scale the VM system upstream, a lot of our hacks are going away. We've got a blog detailing a lot of our work here: https://medium.com/netflix-techblog/serving-100-gbps-from-an-open-connect-appliance-cdb51dda3b99 https://medium.com/netflix-techblog/serving-100-gbps-from-an...