3 ms·

Last time there were Netflix employees claiming Linux can't do more than 60% of FreeBSD's performance in their workloads. Pretty good technical reason if you a

• a012 7y ago
  Netflix has modified FreeBSD networking stacks to serve 100 Gbps at edge. But it's just their secret juice.
  • drewg123 7y ago
    Nothing is secret. AFAIK, everything is upstream in 13-current EDIT: The above applies mostly to the kernel. I've run a vanilla FreeBSD kernel on one of our appliances and gotten good performance (and served at 100Gb/s). In terms of userspace, openssl support for KTLS is only available in OpenSSL's master tree. We'd like to bring them back into the stable OpenSSL that's in FreeBSD's contrib, but we're not sure that's going to happen. And there are some patches to support kTLS with ngninx that are floating around in various forms; I'm pretty sure Mellanox has been giving out a version that should work for FreeBSD as well as Linux ktls.
  • trasz 7y ago
    Same way Google modified Linux to serve whatever they need it to. That’s how Open Source works. (And yet, 60%. Curious.)
• morning_gelato 7y ago
  Could you please provide a link to those discussions/benchmarks regarding 60% performance? In the presentations by Netflix engineers that I have seen, they've primarily cited licensing as the reason they chose FreeBSD over Linux. It would certainly be interesting to see a performance comparison between Netflix's open connect appliances with Google's global cache servers.