From owner-freebsd-stable@FreeBSD.ORG Tue Oct 16 16:58:46 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D39016A417 for ; Tue, 16 Oct 2007 16:58:46 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.freebsd.org (Postfix) with ESMTP id C6A9C13C45B for ; Tue, 16 Oct 2007 16:58:45 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from [81.104.144.87] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Ihpki-0000TC-Gp; Tue, 16 Oct 2007 17:58:44 +0100 Received: from freaky by voi.aagh.net with local (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Ihpki-0001yS-9P; Tue, 16 Oct 2007 17:58:44 +0100 Date: Tue, 16 Oct 2007 17:58:44 +0100 From: Thomas Hurst To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20071016165844.GA6566@voi.aagh.net> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org References: <47137D36.1020305@chistydom.ru> <47140906.2020107@FreeBSD.org> <47146FB4.6040306@chistydom.ru> <47147E49.9020301@FreeBSD.org> <47149E6E.9000500@chistydom.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47149E6E.9000500@chistydom.ru> Organization: Not much. User-Agent: Mutt/1.5.16 (2007-06-09) Sender: Thomas Hurst Cc: Subject: Re: amrd disk performance drop after running under high load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2007 16:58:46 -0000 * Alexey Popov (lol@chistydom.ru) wrote: > So I can conclude that FreeBSD has a long standing bug in VM that > could be triggered when serving large amount of static data (much > bigger than memory size) on high rates. Possibly this only applies to > large files like mp3 or video. I've seen highly dubious VM behavior when reading large files locally; the system ends up swapping out a small but significant amount of various processes, even very small recently active ones like syslogd, for no apparant reason: http://lists.freebsd.org/pipermail/freebsd-stable/2007-September/036956.html I've also seen dubious IO behavior from amr(4), where access to one array will interfere with IO from an independent set of spindles that just happen to be attached to the same card: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/114438 Given the blank looks I've received every time I've mentioned these things I'm guessing they aren't seen by others all that often, but maybe one or both are vaguely relevent to your situation. -- Thomas 'Freaky' Hurst http://hur.st/