Try reducing maxusers to 128. If you have mbuf problems, override
NMBCLUSTERS ( making it 4096 or 8192 should be sufficient ). Sometimes
network mbuf problems on heavily loaded machines are due to too-large
default buffer sizes - if net.inet.tcp.sendspace or recvspace is greater
then 16384, try reducing it to 16384.
If your machine is not using that > 2GB of swap, cap the swap at 1.9GB.
-Matt
Matthew Dillon
<[email protected]>
:I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays
:stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these
:heavily loaded boxen will fall over due to out of MBUFs errors, or
:so I believe.
:
:I'd love to find some real kernel-tuning documentation out there,
:one of my panics is a "pipeinit: cannot allocate pipe -- out of kvm"
:and I can't pull a crashdump due to a DSCHECK error because my
:SWAP is > 2GB.
:
:
:-Troy Cobb
: Circle Net, Inc.
: http://www.circle.net
:
:
:To Unsubscribe: send mail to [email protected]
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
