Date: Mon, 14 Jan 2008 08:53:50 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Dominic Fandrey <kamikaze@bsdforen.de> Subject: Re: FreeBSD's problems as seen by the BSDForen.de community Message-ID: <200801140853.51486.jhb@freebsd.org> In-Reply-To: <47888443.9060300@bsdforen.de> References: <478556AD.6090400@bsdforen.de> <47875131.4040802@FreeBSD.org> <47888443.9060300@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200801140853.51486.jhb>