Jaco Lesch wrote: > This improved performance significantly with a jump from 3600 qps to > 6200 qps and the system was not sluggish with this "workload" at > all. The magic seems to have been the combination of > "outgoing-range" and "num-queries-per-thread", the system load did > drop from 28 to around 21 directly after this change.
can you clarify, is the workload a "production" resolver (so, a real user base that is perhaps really only offering ~6k qps of load), or is this a "benchmark" where the goal is to determine the maximum number of qps that the server can handle? either way, a load average of 21-28 sounds way too high. perhaps solaris has some sort of tool (dtrace?) comparable to the linux "perf" tool that would help pinpoint the cause of the poor performance? -- Robert Edmonds [email protected] _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
