From owner-freebsd-current@FreeBSD.ORG Sat Jan 12 09:11:36 2008 Return-Path: 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 AEF2116A41A for ; Sat, 12 Jan 2008 09:11:36 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE2613C46A for ; Sat, 12 Jan 2008 09:11:36 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from homeKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 01C75405C13; Sat, 12 Jan 2008 10:11:34 +0100 (CET) Message-ID: <47888443.9060300@bsdforen.de> Date: Sat, 12 Jan 2008 10:11:31 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20071203) MIME-Version: 1.0 To: Kris Kennaway References: <478556AD.6090400@bsdforen.de> <478560AE.2000102@FreeBSD.org> <47875131.4040802@FreeBSD.org> In-Reply-To: <47875131.4040802@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD's problems as seen by the BSDForen.de community X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2008 09:11:36 -0000 Kris Kennaway wrote: > Kris Kennaway wrote: >> Dominic Fandrey wrote: >>> The first problem is the unbearable performance many AMD users are >>> suffering >>> for several chipset and CPU generations. Even minimal I/O load on a >>> hard disk >>> suffices to lock up whole systems. Posts on the mailinglists current and >>> stable have often been answered with denial or have simply been >>> ignored. Only >>> on very rare occasions (if at all) have these problems been taken >>> seriously. >> >> Thanks for the feedback. It is hard to respond to the reports of poor >> performance or other problems without specific information though. > > FYI this was not a dismissal, it was an invitation for you to follow up > with the specific problems your members have seen so we can try to > evaluate them. Yes, thank you. I consider the first replies to the mail as very positive and the intention to take us serious and try help us is clear. I'm a bit disappointed the thread has been hijacked by people who want to press their own agenda. The last time I sent a performance complaint to ports@ it resulted in faster code (pkg_install, bsd.ports.mkd), not in license discussions. Anyway, the general description is the following: during a portupgrade the system response time goes up to several seconds or even minutes during a portupgrade. Imagine writing an email and having to wait a minute for your typing to show up. Needless to say, that using a mouse is impossible. This effect how ever is, though best seen there, not limited to X. Ping times to an affected system doing a portupgrade also go up to several seconds (over a cross cable). What I need now is someone to tell me, what to do in order to track the reasons down. It has recently been brought to my attention that there is a tool for creating scheduler traces, which I might ask people to collect, but my unqualified opinion is that it's an interrupt handling problem.