From: David S. <won...@ya...> - 2005-09-24 00:40:55
|
Just so we have some figures to get a handle on this, I did some timing tests on the e17 I got from cvs this morning. This is on my Athlon XP 3000+ with Barton Core, ASUS A7V333 MoBo, 512 MB DDR 333 KingMax RAM, UltraDMA PATA controller and matching hard drives, and nVidia GeForce4 MX 440. While I have swap space, none of it was ever used. The kernel is the standard SuSE 9.3 kernel with all SuSE supplied security updates - 2.6.11.4-21.9 (I updated SuSE just before updating e17). The X is xorg 6.8.2-30, once again standard SuSE 9.3 issue fully patched. The display manager is entranced as per this mornings cvs, with default theme. Some e17 modules where loaded, some where unloaded, default theme is used, but I changed the background to blue-eyed-trees. The timing is started from the end of the fade of the default entranced theme after logging on. Several timings in a row for each case where performed, with the best one listed below, but there was little variation anyway. I added some extra eaps on the number I reported in an earlier email for the lots eaps test. I did this by using e17genmenu to convert EVERY .desktop file on my system, not all of them are apps. With 38 eaps, enlightenment takes 2 seconds to start up. With 2129 eaps, enlightenment takes 20 seconds to start up. Default SuSE setup of KDE 50 seconds. Default SuSE setup of GNOME 25 seconds. Failsafe xterm 1 second. So, 2000 eaps makes e17 almost as slow as GNOME. There are other window managers installed, they are usually between e17's fastest time and GNOME's fastest time. Gdm (GNOMES display manager) starts xterm as fast as entranced starts enlightenment, while kdm (from KDE) is slower still. I didn't test xdm and wdm, both of which come with SuSE. Since Rasterman showed some interest, in fact he laid down a challenge, and while I was in a testing mood, I booted this same machine from a CD copy of My Linux. The DVD drive used for booting is attached to the other IDE controller, which is only UltraDMA 66. From kernel start to usable state took 12 seconds. A lot of that time is due to the IDE hardware or kernel modules just sitting there doing nothing. Some more was soaked up by lots of NIC kernel modules trying to determine what NICS I actually have, something I could probably move to the background post processing. SuSE time to get to a similar state (single user mode, no services started) was 70 seconds. I got a meeting to get to, catch up with you later. -- Stuff I have no control over could be added after this line. Send instant messages to your online friends http://au.messenger.yahoo.com |