How long does it take...
- To install a specific module?
- To install the ISO?
- To recompile all my modules?
These questions get asked a lot by new lunar users and it is a very logical question: Lunar is after all a source distro and requires you to compile all the applications from source, which can sometimes take an extremely long time!
- System(CPU) speed
Double the CPU MHz, and you double the amount of instructions that a system can make per time unit. So, as a rule, a faster CPU results in faster compiles.
- Memory size
Compiling may require large amounts of memory, especially when compiling C++ applications. Generally, a compilation will go 50% faster if you have double the memory. So, if you only have 128MB of memory, you will speed up your compiles by 225% by increasing the amount of memory to 512MB. This might be worth the trip to the hardware store.
- Idle time
Compiling takes a long time. Every second that your system is doing something else, especially interactive tasks, reduces the amount of time that your system can compile applications.
- System architecture and components
Needless to say that a compile on a SATA hard disk is a lot faster than on a ATA-33 system. Especially with larger modules this is a very important factor.
- Parallel make jobs
If you enable multiple parallel make jobs using lunar / Options / Optimize Architecture and you have a machine with more than one processor or core, most modules will build in a lot less time. Similarly if you have multiple machines and make use of distcc to share the build processes among your systems.
Some basic numbers
The following numbers are from a Pentium 4 system running at 2.9 GHz, with 1 GB of memory, which /proc/cpuinfo rates at 5864 bogomips. This was a fairly normal system back in 2005 and if you wish to compare it with your own system, you should keep in mind that this system might be relatively slower or faster based on the influencing factors mentioned earlier.
The modules listed below are very common modules, so they should give you some good insight in how long it takes to compile and install something. Based on the size you can make rough estimates for new modules that you wish to install.
module source size installed size compile time gcc 61540 KB 97188 KB 80m35s glibc 15340 KB 138268 KB 32m47s gtk+-2 18672 KB 64884 KB 15m56s perl 14792 KB 56844 KB 9m43s
However, it is not easy to see whether there is any correlation between source size, installed size and compile time from such a small sample. Not all modules are built and installed in the same way. The gcc compiler has a very elaborate bootstrap phase that takes almost half the time it takes to compile the target compiler. The glibc shown here includes all possible locales. gtk+-2 comes with a lot of bitmaps and documentation. Many many module-specific factors are at work here.
Estimating compile time
If we plot the compile time against the size of the installed product or the source code size (in compressed form easily available), we get a very loose correlation shown in the graph below, where the straight lines are produced using gnuplot's fit function:
The plot shows that there are an awful lot more small modules than large ones in the 400+ modules installed on this machine, but the range of values obscures any details. If we plot the same basic data using LOG values, we get the following graph:
As you can see there is a faint correlation possible using either installed size or source size, but it's more interesting to predict compile times based on source size because once we have the installed size we already know the compile time anyway. Where the source size line crosses the x-axis, LOG(Compile time) is 0.0 and LOG(Source size) is almost 3.0, so Compile time is 1s and Source size is approx 20KB! [Note: that's LOG to base e, not LOG to base 10] This gives you a very crude compile speed of 20 KB/s, and allows you to pre-estimate the compile time, assuming that your system is the same speed as my reference system.
In fact, if I divide the total size of all of the sources by the total compile time, the average compile speed is 24.8 KB/s, so the estimate isn't too far off.
We can do some more elaborate math on this and calculate an "index" for all modules. The index of a module could be easily calculated by dividing the actual compile speed for a module by the average compile speed:
gcc - 61520 KB of compressed source code compiled and installed in 80m35s, i.e. speed is 12.7 KB/s and index is 0.51 glibc - 15340 KB of compressed source code compiled and installed in 32m47s, i.e. speed is 7.8 KB/s and index is 0.31 gtk+-2 - 18672 KB of compressed source code compiled and installed in 15m56s, i.e. speed is 19.5 KB/s and index is 0.80 perl - 14792 KB of compressed source code compiled and installed in 9m43s, i.e. speed is 25.4 KB/s and index is 1.02
We could, of course, do this for all modules, but this would involve someone actually downloading and installing every one of them, and this just isn't realistic as there are currently more than 3600 modules in the moonbase. [I tried to download all modules once using lget -a and it came to 15GB. Using the approximate compile speed of 20KB/s it would take more than 8 days to build everything]
From ISO install to desktop
Just out of curiosity, and for information to others, I decided to time how long it took to install a "minimal" desktop system from scratch from the 1.6.5 ISO on a relatively new system and a 9-year-old relic. I might add this 5-year-old box in the future.
It's clear that you probably don't want to install Lunar on really old hardware, unless you have a lot of patience, or can use
|System||CPUs*bogomips ||RAM||Disk ||Install||lin gcc...||lin linux-2.6||lunar update||lin XOrg7||lin xfce4||TOTAL|
|Acer AX5810||4 * 4988||6 Gb||1681 / 129 MB/s||0h11||1h01||0h12||0h20||0h23||0h14||2h21|
|Vaio FX401||1 * 1600||512Mb||179 / 17 MB/s||0h18||11h26||3h37||2h44||3h12||2h15||23h32|
grep bogomips /proc/cpuinfo
hdparm -t -T /dev/sdX
The basic procedure:
- install from the ISO, and take the pre-compiled kernel, and reboot
lunarand set number of parallel makes to 4 in Options / Optimize Architecture
- do the
lin gcc glibc gcc bash coreutils tar wgetdance from
lin linux-2.6to explicitly build a new kernel, and reboot
lunar updateto rebuild any outdated parts of the core system
lin XOrg7to build X
lin xfce4to build Xfce4
After the first reboot I primed the system by copying sources from /var/spool/lunar on another up-to-date machine to avoid download delays and glitches.
When asked questions about optional depends, etc. I simply hit return to accept the default values. I did not reconfigure the kernel. I used
lin --deps for the XOrg7 and xfce4 builds to pre-answer the questions before kicking off the real builds so I could leave them unattended without adding delays for prompts to timeout.
NOTE: this procedure is for timing purposes only, I still have to go back and install the correct drivers for X, etc.