Date: Mon, 01 Dec 2003 23:15:49 -0700 From: Scott Long <scottl@freebsd.org> To: Jonathan Mini <mini@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: 40% slowdown with dynamic /bin/sh Message-ID: <3FCC2E15.90204@freebsd.org> In-Reply-To: <C2E2964E-248C-11D8-BEFA-000A95CD3CF8@freebsd.org> 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]> <C2E2964E-248C-11D8-BEFA-000A95CD3CF8@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Mini wrote: > 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). I regularly use -s. With the pipe code being completely Giant-free, I don't see a significant performance difference anymore on an SMP machine when the output is not supressed. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FCC2E15.90204>