Date: Tue, 14 Sep 2010 13:33:58 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: is vfs.lookup_shared unsafe in 7.3? Message-ID: <i6nmj5$l5c$1@dough.gmane.org> In-Reply-To: <AANLkTinEje-%2B1P1n33YMKAaciaYHQH%2BdpwgX6UY1dOux@mail.gmail.com> References: <AANLkTinEje-%2B1P1n33YMKAaciaYHQH%2BdpwgX6UY1dOux@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/13/10 22:57, cronfy wrote: > Hello, > > Trying to overtake high server load (sudden peaks of 15%us/85%sy, LA> > 40, very slow lstat() at these moments, looks like some kind of lock > contention) I enabled vfs.lookup_shared=1 on two servers today. One is > FreeBSD-7.3 kernel csup'ed and built Sep 9 2010 and other is > FreeBSD-7.3 csup'ed and built Jul 16 2010. The important think you missed is *where* is the supposed lock contention. If you have lots of processes in "ufs" state, there are other things that can help you, such as increasing vfs.ufs.dirhash_maxmem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?i6nmj5$l5c$1>