Pre-linking binaries is a method of modifying ELF libraries so that the relocation link time overhead is performed not at load time and hence theoretically speeding up program start time (see the Wikipedia entry for more details).
To test this, I installed Karmic 9.10 Alpha 2 on a Dell Inspiron 6400 laptop using ext4 as my default file system and added some instrumentation to measure the time from when the first rc scripts are started to the time the desktop completes loading when auto-logging in.
First, I measured the startup time 5 times without prelinking; this came to an average of 16.397 seconds with a standard deviation of 0.21 seconds.
Next I installed prelink and pre-linked all the system libraries (which takes ~5 minutes) using the following recipe:
- apt-get install prelinkuse apt-get or synaptic to install prelink.
- Open /etc/default/prelink with your favorite editor, using sudo
- Modify PRELINKING=unknown from unknown to yes
- Start the first prelink by running: sudo /etc/cron.daily/prelink
So I am seeing tiny ~0.33% speed up of 0.054 seconds which is within the margin of measuring error. All in all this took me ~1.5 hours to set up and measure, which means that if I boot my laptop once a day it will take me 274 years before I start saving time :-)
All in all it's not really worth enabling prelinking. At least I now know!
(Note: pre-linking may be considered a security issue, as Ubuntu makes use of randomizing the start of code to make it more difficult for rogue programs to exploit.)
I suspect that if the processor was significantly slower and there was less I/O delay (perhaps using SSD rather than HDD) I may actually see more of a significant speed up since prelinking saves some CPU cycles. I speculate that prelinking may be therefore worth considering on lower speed or less powerful platforms such as ARM or Intel Atom based machines.
The next test will be to see if large applications that use tens of libraries start up faster...
No comments:
Post a Comment