From owner-freebsd-geom@FreeBSD.ORG Thu Mar 29 15:58:32 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4F8F16A401 for ; Thu, 29 Mar 2007 15:58:32 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 86CC613C448 for ; Thu, 29 Mar 2007 15:58:32 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l2TFwMio058650; Thu, 29 Mar 2007 10:58:22 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <460BE21E.7070700@freebsd.org> Date: Thu, 29 Mar 2007 10:58:22 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.10 (X11/20070320) MIME-Version: 1.0 To: Ivan Voras References: <003401c7712a$f71ebb60$6502a8c0@peteruj> <005c01c77134$28e0fce0$6502a8c0@peteruj> <86zm5xph7o.fsf@dwp.des.no> <005301c771e4$bb0a3900$6502a8c0@peteruj> <86lkhg5oz5.fsf@dwp.des.no> <007c01c771fe$805b2fc0$6502a8c0@peteruj> <86odmc42mh.fsf@dwp.des.no> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88.4/2961/Thu Mar 29 09:06:01 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-geom@freebsd.org Subject: Re: raid3 is slow X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2007 15:58:32 -0000 On 03/29/07 10:52, Ivan Voras wrote: > Dag-Erling Smørgrav wrote: > >> You don't seem to understand what the load averages mean. They are >> the average number of runnable threads in the scheduler queue over the >> last one, five and fifteen seconds. Certain workloads will drive up >> the load averages without consuming all available CPU time. This is >> particularly the case for workloads where small chunks of data (e.g. >> RAID3 stripes) are passed around between multiple threads. > > But, in his case the threads DO seem to consume much more CPU time than > they should - especially the g_down thread. In this case, load avg ( as > an approximation of real system load) is useful, and he's not concerned > without cause. > > It would be good to see output of a ps -auxl next time he's running the test. Eric