It's been some years now, but I had worked on developing code for a high
throughput network server (not BIND). We found that on multi-socketed
NUMA machines we could have similar contention problems, and it was
quite important to make sure that threads which needed access to the
same memory areas w
On 01/06/2017 23:26, Mathew Ian Eis wrote:
> … and for one last really crazy idea, you could try running a pair of
> named instances on the machine and fronting them with nginx’s
> supposedly scalable UDP load balancer. (As long as you don’t get a
> performance hit, it also opens up other interest
On 02/06/2017 08:12, Browne, Stuart wrote:
> Query rate thus far reached (on 24 cores, numa node restricted): 426k qps
> Query rate thus far reached (on 48 cores, numa nodes unrestricted): 321k qps
In our internal Performance Lab I've achieved nearly 900 kqps on small
authoritative zones when we
On 02/06/17 08:12, Browne, Stuart wrote:
Just some interesting investigation results. One of the URL's Matthew
Ian Eis linked to talked about using a tool called 'perf'. For the
hell of it, I gave it a shot.
perf is super-powerful.
On a sufficiently recent kernel you can also do interesting th
On Thu, Jun 01, 2017 at 04:28:23PM +0200, Job wrote:
> is there a way in Bind 9 to stop logging (to bind.log standard
> file) all the in-addr.arpa queries?
What "standard" is this? The default logging for named goes to
syslog, and from there it's up to your syslogd to decide if/where it
should
Just some interesting investigation results. One of the URL's Matthew Ian Eis
linked to talked about using a tool called 'perf'. For the hell of it, I gave
it a shot.
Sure enough it tells some very interesting things.
When BIND was restricted to using a single NUMA node, the biggest call (to
_
6 matches
Mail list logo
