From owner-freebsd-current@FreeBSD.ORG  Mon Jul 11 16:25:57 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 42F9C106564A;
	Mon, 11 Jul 2011 16:25:57 +0000 (UTC)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.95.76.21])
	by mx1.freebsd.org (Postfix) with ESMTP id 1F05D8FC08;
	Mon, 11 Jul 2011 16:25:57 +0000 (UTC)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
	[127.0.0.1])
	by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id
	p6BGPuVu097631; Mon, 11 Jul 2011 09:25:56 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id
	p6BGPuNR097630; Mon, 11 Jul 2011 09:25:56 -0700 (PDT)
	(envelope-from sgk)
Date: Mon, 11 Jul 2011 09:25:56 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Adrian Chadd <adrian@freebsd.org>
Message-ID: <20110711162556.GB97361@troutmask.apl.washington.edu>
References: <5080.1309971941@critter.freebsd.dk>
	<20110706180001.GA69157@troutmask.apl.washington.edu>
	<4E14A54A.4050106@freebsd.org> <4E155FF9.5090905@FreeBSD.org>
	<20110707151440.GA75537@troutmask.apl.washington.edu>
	<4E160C2F.8020001@FreeBSD.org>
	<20110707200845.GA77049@troutmask.apl.washington.edu>
	<ivf221$oo2$1@dough.gmane.org> <4E1B1198.6090308@FreeBSD.org>
	<CAJ-Vmo=18J7c2CbtAp+=EnZg992KJMbMXeDe=TQz_Ro=iBE2Cg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJ-Vmo=18J7c2CbtAp+=EnZg992KJMbMXeDe=TQz_Ro=iBE2Cg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: freebsd-current@freebsd.org, Ivan Voras <ivoras@freebsd.org>,
	Andriy Gapon <avg@freebsd.org>
Subject: Re: Heavy I/O blocks FreeBSD box for several seconds
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2011 16:25:57 -0000

On Mon, Jul 11, 2011 at 11:42:02PM +0800, Adrian Chadd wrote:
> That top output is averaged and slow to adjust.
> Using "top" as an indication as to what's really going on is likely
> not a good idea.
> 

Restoring top output here:

>   PID USERNAME  THR PRI NICE   SIZE    RES STATE   C   TIME    CPU COMMAND
>  1318 kargl       1 103    0   370M   294M CPU0    0   1:31 100.00% sasmp
>  1319 kargl       1 103    0   370M   294M RUN     1   1:29 100.00% sasmp
>  1322 kargl       1  99    0   370M   294M CPU2    2   1:03 87.26% sasmp
>  1320 kargl       1  91    0   370M   294M RUN     3   1:07 60.79% sasmp
>  1321 kargl       1  89    0   370M   294M CPU3    3   1:06 55.18% sasmp

That TIME column is a very good indication of problem.

I can assure you that wall-clock time for the application
under ULE is far longer than under 4BSD.

IIRC (because its been awhile since I looked at problem), guess
what happens when pid 1318 or 1319 finishes?  Did you guess that
pid 1320 and 1321 are still stuck on the same cpu?

-- 
Steve