Re: 5.2-RELEASE crash

From: Scott Long (scottl_at_freebsd.org)
Date: 01/31/04

  • Next message: Peter Schultz: "Re: Interrupt storm on acpi0 occurred after madt.c change" 
    Date: Sat, 31 Jan 2004 10:46:13 -0700
To: Andy Hilker <ah@crypta.net>

    Andy Hilker wrote:
    > Hi,
    >
    >
    >>Also, the scaling of kern.maxvnodes doesn't work very well. On a large
    >>memory system, it will typically set this to 200,000-300,000. If you
    >>don't need this many, then it is easier to just crank it down to a more
    >>reasonable level than fiddle with the KMEM parameters.
    >
    >
    > And what is reasonable level or how i determine it? :)
    >
    > Andy
    >

    Look at what you are doing with your system. If you're serving a
    high-traffic website with hundreds of thousands of files, you might not
    want to lower the maxvnode limit. If you're only dealing with a small
    working set of files that only spikes occasionally, lowering the limit
    is probably a good thing.

    Scott

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Peter Schultz: "Re: Interrupt storm on acpi0 occurred after madt.c change"