Date: Wed, 28 Aug 2019 02:59:05 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Victor Gamov <vit@otcnet.ru>, "Andrey V. Elsukov" <bu7cher@yandex.ru>, freebsd-net@freebsd.org Subject: Re: finding optimal ipfw strategy Message-ID: <032b67e1-5359-4f00-a449-26c43b70a467@grosbein.net> In-Reply-To: <60d075ee-0d39-6606-ea5a-35e27818162a@otcnet.ru> References: <f38b21a5-8f9f-4f60-4b27-c810f78cdc88@otcnet.ru> <4ff39c8f-341c-5d72-1b26-6558c57bff8d@grosbein.net> <a559d2bd-5218-f344-2e88-c00893272222@otcnet.ru> <ddaa55bc-1fa5-151b-258e-e3e9844802ef@yandex.ru> <c275f853-62a7-6bb7-d309-bf8a27d3dbae@grosbein.net> <50b0748d-bf8a-4de9-58bf-800ddd4f9c27@grosbein.net> <60d075ee-0d39-6606-ea5a-35e27818162a@otcnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
28.08.2019 2:22, Victor Gamov wrote: >> Also, you should monitor interrupt numbers shown by "systat -vm 3" for igb* devices >> at hours of most load. If they approach 8000 limit but not exceed it, >> you may be suffering from this and should raise the limit with /boot/loader.conf: >> >> hw.igb.max_interrupt_rate=32000 > > It's about 5000-7000 per rxq 7000 is quite close considering it is average for quite long period (a second or seconds). It can hit 8000 for some ticks easily in your case. You should raise the limit as soon as possible. I'd advise to double it upto 16000 first but if you cannot afford extra reboot better use 32000 as it's just fine for 1Gbps link.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?032b67e1-5359-4f00-a449-26c43b70a467>