Date: Sun, 12 Aug 2018 18:50:17 +0200 From: Honda Michio <micchie@sfc.wide.ad.jp> To: freebsd-current@freebsd.org Subject: TCP server app performance Message-ID: <CA%2BSc9E3_6bw68odAMH2Y-SzR2-PjuxZG6jp8P0JZV6z9LgmwQw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, I'm measuring TCP server app performance using my toy web server. It just accept TCP connections and responds back HTTP OK to the clients. It monitors sockets using kqueue, and processes each ready descriptor using a pair of read() and write(). (in more detail, it's https://github.com/micchie/netmap/tree/paste/apps/phttpd) Using 100 persistent TCP connections (the client sends 44 B HTTP GET and the server responds with 151 B of HTTP OK) and a single CPU core, I only get 152K requests per second, which is 2.5x slower than Linux that runs the same app (except that it uses epoll instead of kqueue). I cannot justify this by myself. Does anybody has some intuition about how much FreeBSD would get with such workloads? I tried disabling TCP delayed ack and changing interrupt rates, but no significant difference was observed. I use FreeBSD-CURRENT with GENERIC-NODEBUG (git commit hash: 3015145c3aa4b). For hardware, the server has Xeon Silver 4110 and Intel X540 NIC (activate only a single queue as I test with a single CPU core). All the offloadings are disabled. Cheers, - Michio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BSc9E3_6bw68odAMH2Y-SzR2-PjuxZG6jp8P0JZV6z9LgmwQw>