From owner-freebsd-current@FreeBSD.ORG Mon Jan 14 14:32: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 7AD7816A417; Mon, 14 Jan 2008 14:32:36 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 629E913C4CC; Mon, 14 Jan 2008 14:32:36 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id BC5901A4D83; Mon, 14 Jan 2008 06:29:23 -0800 (PST) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 14 Jan 2008 08:53:50 -0500 User-Agent: KMail/1.9.7 References: <478556AD.6090400@bsdforen.de> <47875131.4040802@FreeBSD.org> <47888443.9060300@bsdforen.de> In-Reply-To: <47888443.9060300@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801140853.51486.jhb@freebsd.org> Cc: Dominic Fandrey 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: Mon, 14 Jan 2008 14:32:36 -0000 On Saturday 12 January 2008 04:11:31 am Dominic Fandrey wrote: > 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). Look at /usr/src/tools/sched/schedgraph.py. It has instructions near the top of the file on what kernel options to use and ports to install. -- John Baldwin