Date: Mon, 1 Dec 2003 21:59:59 -0800 From: Jonathan Mini <mini@freebsd.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-current@freebsd.org Subject: Re: 40% slowdown with dynamic /bin/sh Message-ID: <C2E2964E-248C-11D8-BEFA-000A95CD3CF8@freebsd.org> In-Reply-To: <p0600201bbbeecf65f8b1@[128.113.24.47]> References: <200311251214.23290.doconnor@gsoft.com.au> <00a701c3b33c$f798c5e0$b9844051@insultant.net> <20031126052320.GH15294@wombat.localnet> <p06002014bbea2b21766b@[128.113.24.47]> <20031127161940.I77322@gamplex.bde.org> <p0600201bbbeecf65f8b1@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
I have found that the cost of printing the spew often slows down compiles measurably, especially when spewing to an xterm running on a local XFree86 process. Even with syscons, this is noticeable. I generally tend to run my builds behind the screen port these days, which helps (screen implements a virtual display buffer that disconnects screen updates from the display client and the slave pty). Another optimization worth noting is running make -q, which silences a lot of that spam (urban legend has it that the synchronization in parallel makes to write the build messages causes noticeable amounts of contention). On Nov 29, 2003, at 3:22 PM, Garance A Drosihn wrote: > I also had some benchmarks of doing 'buildworld' over an > ssh connection vs doing it at the console. Oddly enough, > the ssh connection was faster in some ways and slower in > others. I wonder if there is a speed-up by writing to a > file instead of the console? -- Jonathan Mini mini@freebsd.org http://www.freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C2E2964E-248C-11D8-BEFA-000A95CD3CF8>