Prelink
Contents |
Introduction
Most programs require libraries to function. Libraries can be integrated into a program once, by a linker, when it is compiled (static linking) or they can be integrated when the program is run by a loader, (dynamic linking). Dynamic linking has advantages in code size and management, but every time a program is run, the loader needs to find the relevant libraries. Because the libraries can move around in memory, this causes a performance penalty, and the more libraries that need to be resolved, the greater the penalty. Prelink reduces this penalty by using the system's dynamic linker to reversibly perform this linking in advance ("prelinking" the executable file) by relocating. Afterward, the program only needs to spend time finding the relevant libraries on being run if, for some reason (perhaps an upgrade), the libraries have changed since being prelinked.
Installing
prelink is currently available in the official repositories.
Configuration
All settings are in /etc/prelink.conf.
Usage
Prelinking
following command prelink all the binaries in the directories given by /etc/prelink.conf
# prelink -amR
Removing prelink
Removing prelinking from all binaries
# prelink -au
Daily Cron Job
This is recommended (and included in other distros packages) as it has to be done in order to get speed benefits from updates. Save as /etc/cron.daily/prelink.cron
/etc/cron.daily/prelink.cron
#!/bin/bash [[ -x /usr/bin/prelink ]] && /usr/bin/prelink -amR &>/dev/null
and give it the necessary ownership and permissions:
# chmod 755 /etc/cron.daily/prelink.cron
KDE
KDE knows about prelinking and it will start faster if you tell it you have it. It is best to stick this in where all the users can use it.
/etc/profile.d/kde-is-prelinked.sh
export KDE_IS_PRELINKED=1
and give it the necessary ownership and permissions:
# chmod 755 /etc/profile.d/kde-is-prelinked.sh