Yes I'm talking about Nginx running on those bsd boxes, they have such a custom design that writing your own static file process would have made sense.
Getting an HTTP server to work with the diversity of HTTP clients in the world that Netflix supports is not going to be fun, and NGINX is right there.
As I understand it, they've made some changes to NGINX, but I don't think they've made a lot, and I don't think anything where the structure of NGINX was not conducive to it or limiting.
I'm not one to shy away from building a custom design, but it's a lot easier when you control the clients, and Netflix has to work with everything from browsers to weird SDKs in TVs.
Netflix OCA performance seems mostly bottlenecked on I/O/memory bandwidth (and cpu overhead for pacing?) and any sensible HTTP server for static files isn't going to use a lot of memory bandwidth processing inbound requests and calling sendfile on static files. So why spend the limited time of a small team to build something that's not going to make a big difference.
