On Mon, Apr 4, 2011 at 1:56 PM, Boris Kochergin <sp...@acm.poly.edu> wrote: > The problem persists, I'm afraid, and seems to have crept up a lot more > quickly than before: > > # uname -a > FreeBSD exodus.poly.edu 8.2-STABLE FreeBSD 8.2-STABLE #3: Sat Apr 2 > 11:48:43 EDT 2011 sp...@exodus.poly.edu:/usr/obj/usr/src/sys/EXODUS > amd64 > > Mem: 314M Active, 955M Inact, 6356M Wired, 267M Cache, 828M Buf, 18M Free > > Any ideas for a diagnostic recourse?
My bet would be that the wired memory is used by ZFS ARC. In your vmstat-m output you can see that ~2.2G were allocated for 'solaris' subsystem. Due to the fact that ARC allocations tend to be random, we do waste a lot of memory on that. There were few patches floating on stable@ adn fs@ that were supposed to mitigate the issue, but so far there's no good out of the box solution. General advice is to tune ARC so that it works in your case. Key loader tunables are vfs.zfs.arc_min and vfs.zfs.arc_max. Don't set min too high and experimentally set max to the maximum value that does not cause problems. One of the factors that makes things noticeably worse is presence of i/o actifity on non-ZFS filesystems. Regular filesystems cache competes with ZFS for RAM. In the past ZFS used to give up memory way too easily. Currently it's a bit more balanced, but is still far from perfect. By the way, if you don't have on-disk swap configured, I'd recommend adding some. It may help avoiding processes being killed during intermittent memory shortages. If would also help if you could post your /boot/loader.conf and output of "zfs-stats -a" (available in ports). --Artem _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
