On Thu, 19 Nov 2020 09:30:14 +0100 Björn Töpel wrote: > Performance netperf UDP_RR: > > Note that netperf UDP_RR is not a heavy traffic tests, and preferred > busy-polling is not typically something we want to use here. > > $ echo 20 | sudo tee /proc/sys/net/core/busy_read > $ netperf -H 192.168.1.1 -l 30 -t UDP_RR -v 2 -- \ > -o min_latency,mean_latency,max_latency,stddev_latency,transaction_rate > > busy-polling blocking sockets: 12,13.33,224,0.63,74731.177 > > I hacked netperf to use non-blocking sockets and re-ran: > > busy-polling non-blocking sockets: 12,13.46,218,0.72,73991.172 > prefer busy-polling non-blocking sockets: 12,13.62,221,0.59,73138.448 > > Using the preferred busy-polling mode does not impact performance. > > The above tests was done for the 'ice' driver. Any interest in this work form ADQ folks? I recall they were using memcache with busy polling for their tests, it'd cool to see how much this helps memcache on P99+ latency!
