On 9 Jul 2020, at 21:25, Havard Eidnes via bind-users wrote:
> 2e#1) Make sure your UDP socket *receive* buffers are big enough.
> If on BSD, monitor for "dropped due to full socket buffers"
> count in "netstat -s" output, and tune accordingly. Note that
> this may be a symptom
These suggestions - like most performance articles - are oriented toward
achieving the highest performance with large configurations. E.g. "How
big can/should you go to support big loads?"
That's useful for many users. But there are also many people who run
smaller operations, where the goal is
> OS settings and the system environment
...
> 2e) Make sure your socket send buffers are big enough. (not
> sure if this is obsolete advice, do we need to tell people how
> to tell if their buffers are causing delays?)
2e#1) Make sure your UDP socket *receive* buffers are big enough.
On 2020-07-07 20:57, Victoria Risk wrote:
A while ago we created a KB article with tips on how to improve your
performance with our Kea dhcp server. The tips were fairly obvious to
our developers and this was pretty successful. We would like to do
something similar for BIND, provide a dozen or so
On 7/7/2020 5:57 PM, Victoria Risk wrote:
A while ago we created a KB article with tips on how to improve your
performance with our Kea dhcp server. The tips were fairly obvious to
our developers and this was pretty successful. We would like to do
something similar for BIND, provide a dozen or
Just one quick one before I run off to lunch with regards to section 2:
- Try to avoid crossing NUMA boundaries. At high throughput, the context
switching and far memory calls kills performance.
Stuart
From: bind-users on behalf of Victoria Risk
Date: Wednesday, 8 July 2020 at 11:58
To: bind
6 matches
Mail list logo
