Re:Pushing the Limits of Kernel Networking
by toast0 on Friday October 02, 2015 @02:36AM
(#10317042)
> But it might also help when the machine is performing a service which requires very little CPU time but moves huge amounts of data. Like serving video. Are the big video servers still x86 machines, or does Netflix now use custom hardware?
Netflix is using x86 for their video servers. They're running FreeBSD, and they've published recently[1] about moving TLS session crypto into the kernel so they can serve their videos with TLS without as much of a performance loss. The pdf mentions they were able to get 40 Gbps out of their machines with TLS disabled; with TLS enabled, they were only able to get close to 10 Gbps. CPU is E5-2650L (Sandy Bridge), serving from SSD, equipped with quad port 10g nic.
Re:Pushing the Limits of Kernel Networking
by stephengillie on Friday October 02, 2015 @10:51AM
(#10318912)
It's interesting, that CPU has the AES new instructions, so it can hardware accelerate AES operations. Yet TLS is so impacting.
Re:Pushing the Limits of Kernel Networking
by acconsta on Friday October 02, 2015 @05:01PM
(#10321305)
Even with the intrinsics AES is pretty expensive
https://software.intel.com/en-us/articles/intel-aes-ni-perfo...
Right. This is for the case where the machine isn't doing anything with the packet except sending it back out. But it might also help when the machine is performing a service which requires very little CPU time but moves huge amounts of data. Like serving video. Are the big video servers still x86 machines, or does Netflix now use custom hardware?
If it's a web server constructing pages on the fly from a database, that work will dominate the time spent getting the packets in and out of the machine.