This is a good theory, because RRD data from 2.2.6 suggests that the
difference in utilization between the versions is slight, and that we
had 'barely' exhausted our system default allocation.
Is there a difference between nano and full with respect to the
installer explicitly setting tunables for kern.ipc.nmbclusters and
kern.ipc.nmbuf? Vick Khera says he sees explicitly set tunables on his
2.3.2 system, yet my virgin installation of Nano pfSense 2.3.2 has no
explicit declarations?
Vick, is your Supermicro A1SRi-2758F running an installation that came
from Netgate, or is it a community edition installation? If the latter,
Full or Nano?
On 1/25/2017 3:49 PM, Jim Pingle wrote:
On 01/25/2017 01:10 PM, Karl Fife wrote:
The piece that's still missing for me is that there must have been some
change in default system setting for FreeBSD, or some other change
between versions, because the system booted fine with pfSense v 2.2.6
Aside from what has already been suggested by others, it's possible that
the newer drivers from FreeBSD 10.3 in pfSense 2.3.x enabled features on
the NIC chipset that consumed more mbufs. For example, it might be using
more queues per NIC by default than it did previously.
Jim
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
