In exploring the difference in performance to Windows on the same hardware, we came across another fault we've not been able to advance.
The machine is 'vintage' Hewlett Packard Proliant DL320s (Storage) server that has a 12 (or 14) bay LFF SAS backplane and is easily capable of sustained 100Mbytes/sec performance even though it has a max of 8Gb RAM and a crappy Xeon 3060 dual-core processor, using the Smart Array P400 controller in RAID 6. The gigabit adapters are dual Broadcom 5704 series.
Windows supports jumbo packets on the LAGGed adapter no problems for a nice performance bump.
Adding "mtu 9000" to the member adapters of the FreeNAS LAGG seems to be OK until a reboot. The server throws a message "no memory for std Rx buffers" and the links are DOWN.
We've tried Autotune and A LOT of FreeBSD networking tuning reading, specifically this page of variables and explanations.
We're kinda exhausted and wondered if there are any FreeBSD kernel/dev gurus that might have hints on where to explore what-on-earth is going on.
The machine is 'vintage' Hewlett Packard Proliant DL320s (Storage) server that has a 12 (or 14) bay LFF SAS backplane and is easily capable of sustained 100Mbytes/sec performance even though it has a max of 8Gb RAM and a crappy Xeon 3060 dual-core processor, using the Smart Array P400 controller in RAID 6. The gigabit adapters are dual Broadcom 5704 series.
Windows supports jumbo packets on the LAGGed adapter no problems for a nice performance bump.
Adding "mtu 9000" to the member adapters of the FreeNAS LAGG seems to be OK until a reboot. The server throws a message "no memory for std Rx buffers" and the links are DOWN.
We've tried Autotune and A LOT of FreeBSD networking tuning reading, specifically this page of variables and explanations.
We're kinda exhausted and wondered if there are any FreeBSD kernel/dev gurus that might have hints on where to explore what-on-earth is going on.