Slashdot Mirror


Optimizing KDE 3.1.x

David Lechnyr writes "This article goes into detail on optimizing KDE for speed. Typically, most distributions include pre-compiled binaries of KDE which are optimized for an Intel i386 computer. Chances are that you're running something faster than this; if so, this should help you tweak the compile process to speed things up a bit."

3 of 83 comments (clear)

  1. prelink by dotgod · · Score: 4, Interesting

    Using prelink will also provide additional optimization.

  2. I do this with ALL my software, automatically. by ewomack · · Score: 5, Interesting

    See http://www.sourcemage.org/ All source, downloaded from the authors site and compiled to the settings and optimizations YOU choose.

  3. Re:portage ? by dh003i · · Score: 4, Interesting

    Experimental? Come on. Maybe -O3 and then a series of other additional optimizations beyond that are experimental. But the sane optimizations most people use are not experimental. I, myself, default to:

    -march=athlon-tbird -Os -pipe -fomit-frame-pointer

    Btw, compiling everything from scratch is hardly "unstable". That's what FreeBSD does. Furthermore, memory optimizations often-times increase system-stability, by reducing the likelihood of situations where there isn't enough RAM. Furthermore, some of the USE settings increase stability by eliminating compiled-in support for crap that you don't use. If you don't use something, and support for it is compiled in, it's just useless crap that has the potential to reduce stability.