Missing item to get KDE start faster

medo · 02-26-2007, 12:26 PM

Hi,

While I am trying to get my lovely KDE to start faster, I read that the directive "Preloader" listed under [X-*-Greeter] section in the file /etc/kde3/kdm/kdmrc can fasten KDE startup. The value for this is set to /usr/bin/preloadkde but that file doesn't exist. Searched for it on my box but could not find it. I am not sure what package should I install to get that functionality back. Was this preload thing obsolete ??
I searched the web but it seems to me that I am the only one noticed this !!

I am using Kubuntu 6.10 (Edgy).

cheers

craigevil · 02-27-2007, 11:29 PM

Not sure abnout *buntu, but the only thing I can find relating to preload in Debian Sid is:
preload - adaptive readahead daemon
ld.so.preload-manager - A utility to manage the libraries in /etc/ld.so.preload

Other than actual programs like Konqueror and OpenOffice:
/usr/lib/debug/usr/lib/kde3/kded_konqy_preloader.so
/usr/lib/kde3/kded_konqy_preloader.la
/usr/lib/kde3/kded_konqy_preloader.so
/usr/lib/openoffice/program/libpreload680li.so
/usr/lib/openoffice/program/resource/preload680en-US.res
/usr/lib/preloadable_libintl.so
/usr/lib/wine/wine-preloader
/usr/share/apps/quanta/templates/scripts/javascript/preload.js
/usr/share/autostart/konqy_preload.desktop
/usr/share/services/kded/konqy_preloader.desktop

Other than maybe prelink - ELF prelinking utility to speed up dynamic linking, which does help programs start a bit faster.

You can get KDE to start faster by only having the services you need running.

My system is crap and I can cold boot to the KDE desktop in around 30 seconds.

I assume you have already tried the suggestions here:
KDE Wiki : Performance Tips
http://wiki.kde.org/tiki-index.php?p...g_startup_time

medo · 02-28-2007, 10:05 AM

Hi craigevil,

Thanks for trying to help. Actually I am ware of all what you mentioned. Thanks for mentioning that wiki link, coz that is the link started my problem. The problem is Why the file /usr/bin/preloadkde does not exist in my Kubuntu.

Where can I find that file?
Do you have it on your computer? (try #locate preloadkde)
Is there a package that I can install that would get it for me? (I tried apt-file search preloadkde but nothing there).

I could've sent this problem to *buntu forum but I wanted other distros to check their packages too.

Cheers

nx5000 · 02-28-2007, 12:08 PM

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407849

Looks like nobody has been able to prove that it's quicker with preloadkde.

It's not available in any repository for debian.

PTrenholme · 02-28-2007, 01:44 PM

Um, I just read the WiKi, and, as far as I could see, the preloadkde to which reference was made is a script that you are supposed to write containing the command that was shown in the WiKi. Something like this:

Code:

#!/bin/bash
basedir=/usr/share
etcdir=/etc
exec find $etcdir/kde3 ~/.kde $basedir/applications \
    $basedir/applnk $basedir/mimelnk $basedir/services \
    $basedir/servicetypes $basedir/config \
    $basedir/icons /opt/kde3/

which you write (changing the paths to each place as needed for your distribution and installation of KDE) and make executable. Then you need to edit he kdmrc script to run the script you created. Note that it does not need to be called preloadkde since any name can be used.

nx5000 · 02-28-2007, 03:44 PM

Ok interesting...
I wonder what it does in fact

It initialise the inode cache by making a find or what?

medo · 02-28-2007, 03:52 PM

Thanks everyone,

I created a script file under /usr/bin/preloadkde. Though I am not sure if it helps, hope it has no bad side effects. I think KDE developers should make some -scientific- benchmarking on the effectiveness of such script. If it fasten the process then add it to the package, if not then update their Wiki.

@nx5000, I think the find command is used to load those files to RAM not to search for something in them.

PTrenholme · 02-28-2007, 09:14 PM

Quote:

Originally Posted by medo

<snip>
@nx5000, I think the find command is used to load those files to RAM not to search for something in them.

Well, yes, in a way. As was explained in the WiKi, what you're doing is "preloading" the hard disk read-ahead cache. What the "find" command does is to force a directory read for the named items, and, because it was read, the initial inode is placed in the cache (which, by default, is all available RAM not used by some program). Then when KDM needs to actually read the file, the physical read can start from a RAM reference rather than a physical read.

While this is somewhat faster, I suspect that the real impact of this step on load time will be almost negligible. But it probably won't hurt anything.

medo, did you remember to add the reference to the script to the kdmrc script? (You didn't mention that you'd done that necessary step, although -- if you were getting an error message about a missing script file -- you'd already made that chnage.) And, did you confirm that the script works correctly by executing it "by hand" in a terminal window? When it's run by itself, it should just list the files in its arguments -- with no error messages.

medo · 02-28-2007, 09:37 PM

@nx5000,

Thanks for the reminder. I did not add reference to the script file becuse its already there by default installation. I run the script from a terminal with no errors.

Have a nice day