Mon Mar 22 11:19:09 PDT 2010
From: Francois Tigeot <ftigeot at wolfpond.org>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Mon, 22 Mar 2010 19:17:45 +0100
List-Post: <mailto:bugs at crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request at crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request at crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request at crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs at crater.dragonflybsd.org>
Content-Type: text/plain; charset=us-ascii
References: <201003201834.o2KIYJ4h004349 at apollo.backplane.com> <20100320184452.GA1507 at sekishi.zefyris.com> <1240.220.233.36.106.1269126548.squirrel at webmail.exetel.com.au> <201003202324.o2KNOrlX006114 at apollo.backplane.com> <13184.108.40.206.106.1269129077.squirrel at webmail.exetel.com.au> <201003211824.o2LIOZUs015643 at apollo.backplane.com> <20100321190708.GA63881 at sekishi.zefyris.com> <201003211914.o2LJEBNo016061 at apollo.backplane.com> <20100322083907.GA1801 at sekishi.zefyris.com> <20100322110225.GA1925
In-Reply-To: <20100322110225.GA1925 at sekishi.zefyris.com>
Sender: bugs-errors at crater.dragonflybsd.org
Errors-To: bugs-errors at crater.dragonflybsd.org
X-Trace: 1269282099 crater_reader.dragonflybsd.org 55374 220.127.116.11
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:11561
On Mon, Mar 22, 2010 at 12:02:25PM +0100, Francois Tigeot wrote:
> On Mon, Mar 22, 2010 at 09:39:07AM +0100, Francois Tigeot wrote:
> > On Sun, Mar 21, 2010 at 12:14:11PM -0700, Matthew Dillon wrote:
> > >
> > > I'd like to know if this solves your particular problem (the paging
> > > issue, not the crashing issue), and if so I will change the default
> > > cycle point for the release. So play with it.
> > With vfs.vm_cycle_point = 40 my server was much more responsive this morning.
> > Almost no programs had to be paged in when first accessed.
> > I have now decreased vm_cycle_point to 32.
> With 32 the situation is slightly worse: some processes are once again paged
> out when not constantly accessed.
> I'm currently testing with vfs.vm_cycle_point = 36.
36 is slightly better but one of the running applications was still massively
paged out after a few hours.
I vote for setting vfs.vm_cycle_point to 40.
More information about the Bugs