From owner-freebsd-ports@FreeBSD.ORG Fri Feb 13 16:03:28 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C2F9106564A; Fri, 13 Feb 2009 16:03:28 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from vps.kc8onw.net (jonathanstewart-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:71d::2]) by mx1.freebsd.org (Postfix) with ESMTP id E99588FC1B; Fri, 13 Feb 2009 16:03:27 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from [10.70.3.246] (in-67-236-184-169.dhcp.embarqhsd.net [67.236.184.169]) by vps.kc8onw.net (Postfix) with ESMTPSA id A69471703C; Fri, 13 Feb 2009 06:34:15 -0500 (EST) Message-ID: <499599C7.3060209@kc8onw.net> Date: Fri, 13 Feb 2009 11:03:19 -0500 From: Jonathan User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Nikolay Tychina References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, makc@FreeBSD.org Subject: Re: FreeBSD Port: ktorrent-3.1.6_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 16:03:28 -0000 Nikolay Tychina wrote: > Hello, > > i installed ktorrent3 and it seems to be very slow while checking pieces. > (~2mb per second) > (Deluge do it much more faster, i didn't try any other clients though) > Do you have the same problem? Same issue here. I get ~4MB/s or so. I started digging around and found that according to gstat (output at end) ktorrent is writing 50-60MB/s to ad18, which is my boot drive, sustained. Most of the other drives in the system are completely idle and belong to the ZFS pool the torrent data is actually on. I've checked using fstat and lsof and nothing leaps out at me. I also watched disk and swap space usage during the check and see nothing changing despite the apparent massive write load. I even tried doing a ktrace + kdump and searching for "write" but didn't find anything there either. I don't claim to be any expert with any of those tools though. Does anyone have any ideas on what to look at next? Thanks, Jonathan dT: 1.035s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 0 0 0 0.0 0 0 0.0 0.0| ad8 0 0 0 0 0.0 0 0 0.0 0.0| ad8s1 0 34 0 0 0.0 32 43 0.5 5.1| ad16 0 0 0 0 0.0 0 0 0.0 0.0| ad8s1a 0 0 0 0 0.0 0 0 0.0 0.0| ad8s1c 0 0 0 0 0.0 0 0 0.0 0.0| acd0 1 3684 0 0 0.0 3684 58921 0.2 81.8| ad18 1 3684 0 0 0.0 3684 58921 0.2 83.2| ad18s1 0 36 0 0 0.0 34 39 2.1 9.2| ad10 0 29 0 0 0.0 27 33 1.1 7.9| ad12 0 34 0 0 0.0 32 43 0.4 5.5| ad14 1 3684 0 0 0.0 3684 58921 0.2 85.8| ad18s1a 0 0 0 0 0.0 0 0 0.0 0.0| ad18s1b 0 0 0 0 0.0 0 0 0.0 0.0| ad18s1c 0 34 0 0 0.0 33 83 3.0 6.0| da0 0 0 0 0 0.0 0 0 0.0 0.0| ad20 0 37 0 0 0.0 36 78 3.4 6.9| da1 0 36 0 0 0.0 35 83 2.3 5.9| da2 0 41 0 0 0.0 40 69 3.4 7.6| da3