MBUF usage at 87%

stephenw10

We were discussing that internally just recently. In testing the limit was not reached apparently but as always the real world can be different to the test bench. You're not the first person to query that setting.
It's likely that value will be set higher by default in future releases for the SG series. If you run real world tests and come to a conclusion about a suitable value we'd love to hear it.

Steve

Edit: managed to leave out an entire word there!

got0

I'm still in playing and testing mode. Currently, it's 28090 and raising step for step with my changes. But I'll tell you once the value has settled.

almabes

From what I have learned working with supermule on DDosing pfSense, there are major architectural differences between the two Intel gigE drivers, em and igb.

The long and the short of it is Intel cards that use the igb driver set up more queues, which require more mbufs than the older em driver. I have also read somewhere, that there is talk of Intel rewriting the em driver to make it more scalable, and more like the igb driver.

jimp

For 2.2.3 we bumped up the default mbuf allocation on the 4860 and its relatives.

You can adjust the nmbclusters value as described at https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards – though one change: We have found that it's also able to be adjusted "live" by adding it as a system tunable. Used to be it only worked as a loader.conf(.local) value but not any more.

pfcode

@jimp:

though one change: We have found that it's also able to be adjusted "live" by adding it as a system tunable. Used to be it only worked as a loader.conf(.local) value but not any more.

Hi,

I couldn't find it (kern.ipc.nmbclusters) in System->Advantage->System tunable list, using 2.2.3

jimp

It's not there by default, that list isn't limited though. Click + to add it in and set whatever value you want.

pfcode

@jimp:

It's not there by default, that list isn't limited though. Click + to add it in and set whatever value you want.

Oh, I c, Thanks.

got0

For SG-4860, you bumped nmbclusters to 26584 in 2.2.3? That's still too close to the max values I witnessed while playing on my box:

max current = 26.60K
max total= 28.09K

I go with 32K to have a stable box.

jimp

It's not corrected on upgrade, new install only. The 4860 units should probably have 2-4x that value, give or take, minimum.

dennypage

So, what is the value that is being chosen on new installs for the SG-4860?

[I've just upgraded my SG-2400 to a SG-4860, but I'm am using the same drive & essentially same config that was in the SG-2440]

Thanks.

@jimp:

It's not corrected on upgrade, new install only. The 4860 units should probably have 2-4x that value, give or take, minimum.

got0

@jimp:

It's not corrected on upgrade, new install only.

What is the recommended upgrade method to get such tuning parameters after an install? Re-installing an SG-* box for each new version of pfsense is not the way, is it?

stephenw10

Create the file /boot/loader.conf.local
Add to it the line:

kern.ipc.nmbclusters="131072"

Or whatever value you want. As described here: https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#mbuf_.2F_nmbclusters
Reboot to see the new value loaded.

Steve

robi

I remember reading somewhere that it's not needed to mess around with /boot/loader.conf.local anymore.
Creating a new system tunable also works. If it does, that would be better, because it's also stored in the config file, which means it's preserved for the future.

stephenw10

Good point. Jim wrote that in this thread: https://forum.pfsense.org/index.php?topic=92253.msg532431#msg532431
I guess I'm too used to using loader.conf.local. ::)

Steve

robatwork

This seems to be the latest post on MBUF - just to note that in 2.3.2 you can add the kern.ipc.nmbclusters variable in system tunables and it takes effect immediately without needing a reboot. Worked well for me

jimp

There is still an advantage to putting the value in loader.conf.local, however. If the hardware requires more mbufs to properly initialize at boot time, it may not be able to do so if you have only set the value as a tunable. If the problem is that the usage increases with load after boot time, then it is OK to use a tunable.