accept(2)/close(2) performance on DragonFly-1ae4ae5

Sepherosa Ziehau sepherosa at
Tue Jun 7 05:52:43 PDT 2016

The network configuration and various settings (tunables/sysctls) are same as:

The accept(2)/close(2) performance is measured w/:

Server side runs:
kq_accept_server -p 7000 -i 16 -r -B (SO_REUSEPORT and process CPU
binding according to getsockopt(SOL_SOCKET,SO_CPUHINT))

Two clients run the following command at the same time:
kq_connect_client -4 ADDR -p 7000 -i 8 -c X -l 600 -B (X = {64,128,256,512})

The result (600s average):
1024 concurrent connections: 494Kconns/s
2048 concurrent connections: 514Kconns/s
4096 concurrent connections: 576Kconns/s
8192 concurrent connections: 580Kconns/s

Contention rate is pretty low (1000/s ~ 2000/s).  Almost no CPU time
is left on CPUs having netisrs @8192 concurrent connections, but the
system is pretty responsive and systat output is smooth.


Tomorrow Will Never Die

More information about the Users mailing list