Date: Sat, 12 Jan 2008 10:11:31 +0100 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD's problems as seen by the BSDForen.de community Message-ID: <47888443.9060300@bsdforen.de> In-Reply-To: <47875131.4040802@FreeBSD.org> References: <478556AD.6090400@bsdforen.de> <478560AE.2000102@FreeBSD.org> <47875131.4040802@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47888443.9060300>