On Thu, 2005-01-06 at 14:51 +0000, Daniel Drake wrote: > Good idea. Here's a few: > [snip] > Use make -jX to get multiple compilations happening at once. I think most > places suggest an X value of one more than your CPU count. Don't overdo that. Using -jX for X>3*CPU you usually get lower performance (cpu cache trashing, memory exhaustion). Also, some ebuilds still revert to -j1
> gcc 2.95 is quite a bit smaller than gcc3, uses less memory, and is a fair > bit > quicker at compiling C code (although the resulting binaries are perhaps not > quite as optimized). On slow/low-memory environments like my laptop this can > be quite handy. Note that gcc2 sucks for C++ :) I wonder how big the differences in code generation are? (correctness, speed, ...) > Make sure DMA is enabled on hard disks, and that support for the systems IDE > controller is compiled into the kernel, and that the appropriate IDE driver > is > being used (and generic IDE is not). ... and hope that your crappy board doesn't always fall back to PIO modes :-) using SCSI / FC / ... should give better and more consistent performance.
signature.asc
Description: This is a digitally signed message part
