Amarok takes a while to load and I was wondering if I could speed it up by loading some of the kde stuff when fvwm starts (I also use some other kde programs).
Since I don’t really care how long fvwm takes to load, I was wondering if there are other things I can run at startup to make the system run faster later on.
nicooo:
Amarok takes a while to load and I was wondering if I could speed it up by loading some of the kde stuff when fvwm starts (I also use some other kde programs).
Since I don’t really care how long fvwm takes to load, I was wondering if there are other things I can run at startup to make the system run faster later on.
You could look at trying to use the “preload” program, or use something other than Amarok.
– Thomas Adam
A possibility is to run “konqueror --preload” somewhere in your config. I don’t think it will delay the startup of fvwm in any noticeable way since that’s done on the background.
preload looks good, hopefully it works as well as it sounds.
I don’t have konqueror installed, seems that amarok only depends on kdelibs. I guess the file browser doesn’t need konqueror.
I still use some KDE applications (konqueror, kmail, k3b,…), and I have this line in my startfunction:
+ I Test (Init) Exec exec kdeinit
This is taken from KDE performance tips :
KDE applications usually require several small KDE daemons (kdeinit, dcopserver, klauncher, kded) to be running. These daemons are launched during first phases of KDE startup, so they are normally available in a KDE session. However when a KDE application is launched outside of KDE, and these daemons are not running (i.e. no other KDE application is running), they need to be launched first. This makes the startup of the KDE application somewhat longer. Since the daemons automatically terminate after a small delay when the last KDE application running exits, repeated usage of a single KDE application outside of KDE can make its startup appear longer than it really is.
In order to avoid this, KDE daemons can be launched manually, in which case they will remain running even if no KDE application is running. This can be achieved by running ‘kdeinit’. This command should be launched in some startup script, or specified as startup command in the GUI used (using some equivalent of KDE’s Autostart folder).
Cheers!