From owner-freebsd-stable@FreeBSD.ORG Wed Feb 13 08:02:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DFD43F3D for ; Wed, 13 Feb 2013 08:02:24 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5FFB4130 for ; Wed, 13 Feb 2013 08:02:24 +0000 (UTC) Received: from ppp247-71.static.internode.on.net (HELO leader.local) ([203.122.247.71]) by ipmail05.adl6.internode.on.net with ESMTP; 13 Feb 2013 18:32:23 +1030 Message-ID: <511B488D.9080809@ShaneWare.Biz> Date: Wed, 13 Feb 2013 18:32:21 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Philipp-Joachim Ost Subject: Re: 9.1 AMD64 multitasking efficiency low References: <511AC154.80409@smo.de> In-Reply-To: <511AC154.80409@smo.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, CeDeROM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 08:02:24 -0000 I have two WD's a 1TB and a 2TB. Upgraded to 9.1 three days ago and don't think it is any worse than 9.0. I find things slow down if two things are trying to access the drive at the same time and when I do get some swapping it gets unbearable. One thing that always annoyed me was the security scans that start early morning, they make any tinderbox builds I leave running grind to a halt. They also run shortly after startup - and they show little cpu usage. Disable them by adding to /etc/periodic.conf daily_status_security_chksetuid_enable="NO" daily_status_security_neggrpperm_enable="NO" I'm sure the first one is a long scan but haven't verified the second. I think I recall the aio module made a difference for me. I believe kldload aio will make it active straight away - if not aio_load="YES" in /etc/loader.conf to load at boot I have a desktop machine - ASUS P8H61-M/LE corei5 8GB ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 3.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich4 bus 0 scbus2 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad8