Results 336 comments of Miek Gieben

Stuff that I'm seeing *might* be because everything is local. Pondering how I can test with an actual network.

Done on Debian 8 - with really *old* 3.16 kernel

udp.go does (localhost): ~~~ Queries per second: 360485.732524 qps ~~~

Can't get NSD to give me reliable figures though :( NSD version 4.1.0 ~~~ root@2:~/prof/perf-tests/local-perf# make TIME=3 queryperf ./bin/queryperf-linux_amd64 -d domain.lst.queryperf -l 3 -s 127.0.0.1 -p 1053 DNS Query Performance...

Some simple queryperfing to get baseline: 0.2: Queries per second: 58800.788936 qps 0.3: Queries per second: 74555.654706 qps

Doing SO_REUSEADDR did *not make any impact at all*! `REUSEPORT` even made performace worse, don't know what I saw in #4, but can't easily replicate it.

Profile out when profiing: All this is done against the n1-standard-4 instance Queries per second: 51117.913849 qps ~~~ % go tool pprof pprof.coredns.localhost:6053.samples.cpu.001.pb.gz ~/pprof deb Entering interactive mode (type "help"...

This looks pretty OK-ish. ~~~ pprof) cum (pprof) top10 10.57s of 48.35s total (21.86%) Dropped 209 nodes (cum = 9.85s) flat flat% sum% cum cum% 0 0% 0% 35.03s 72.45%...

Uploading the profile [pprof.coredns.localhost:6053.samples.cpu.001.pb.gz](https://github.com/coredns/perf-tests/files/987048/pprof.coredns.localhost.6053.samples.cpu.001.pb.gz)

Looking at the web view `syscall.Syscall` again stands out.