begin quote On Wed, 5 Jan 2005 22:55:12 +0000 Stuart Herbert <[EMAIL PROTECTED]> wrote:
> Hi, > > I'd like to put together a doc full of advice on what users can do to > reduce how long it takes to build packages. I'm sure that there's > plenty of you with your own opinions on this, so let's have it ;-) > > To get started ... make /var/tmp/portage a separate filesystem, and > stripe it across multiple disks. ext2, async mount, noatime for compiling. Make sure your swappiness is rather low (more cache! more cache! ;) if on IDE, keep sources+system on one disk, and compile on another, separate the two IDE channels. Then its a read IO from one, and write to the other, which cuts down on seek times. if you need to log, have logs on another disk than you compile from compile on a dedicated partition that never runs out of space, 10 gig ext2 is good for most things. for smaller things, just use a tmpfs, cut down on buffer cache and be happy. tmpfs->swap is worse than ext2, tmpfs -> no swap is better than ext2.. keep ccache on another drive than you compile on. Recuces seektimes. Watch out for IO spiking applications, spamassassin fex. use rxvt or xtrem without AA fonts (somone else suggested this already) as they scroll about 5x faster. and with less cpu usage. Kill all RAMhogs. Evolution, mozilla, gdesklets, superkaramba and so on. (python applications too ;) //Spider -- begin .signature Tortured users / Laughing in pain See Microsoft KB Article Q265230 for more information. end
pgp5HOBdgCOEo.pgp
Description: PGP signature
