Re:Be your own video hoster with Docker and Nginx
by nl on Saturday January 09, 2016 @11:07PM
(#10874098)
There are millions of Ngnix on Linux production implementations.
And your advice is to use experimental[1] Docker support in FreeBSD, when Nginx would be running inside Docker on top of FreBSD's Linux compatibility layer.
Finally - and most critically - Ngnix introduced thread pools to specifically work around a limitation of Linux's async IO implementation:
Although Linux provides a kind of asynchronous interface for reading files, it has a couple of significant drawbacks. One of them is alignment requirements for file access and buffers, but NGINX handles that well. But the second problem is worse. The asynchronous interface requires the O_DIRECT flag to be set on the file descriptor, which means that any access to the file will bypass the cache in memory and increase load on the hard disks. That definitely doesn’t make it optimal for many cases.
To solve this problem in particular, thread pools were introduced in NGINX 1.7.11.[2].
And your advice is to use experimental[1] Docker support in FreeBSD, when Nginx would be running inside Docker on top of FreBSD's Linux compatibility layer.
Finally - and most critically - Ngnix introduced thread pools to specifically work around a limitation of Linux's async IO implementation:
Although Linux provides a kind of asynchronous interface for reading files, it has a couple of significant drawbacks. One of them is alignment requirements for file access and buffers, but NGINX handles that well. But the second problem is worse. The asynchronous interface requires the O_DIRECT flag to be set on the file descriptor, which means that any access to the file will bypass the cache in memory and increase load on the hard disks. That definitely doesn’t make it optimal for many cases.
To solve this problem in particular, thread pools were introduced in NGINX 1.7.11.[2].
[1] https://wiki.freebsd.org/Docker
[2] https://www.nginx.com/blog/thread-pools-boost-performance-9x...