<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.16.0"> </HEAD> <BODY> Darn, sorry for replying late, I forgot to check my mailing list accounts :( Le mardi 25 septembre 2007 à 09:57 +0200, Sebastien Bacher a écrit : <BLOCKQUOTE TYPE=CITE> <PRE> Le lundi 24 septembre 2007 à 17:32 -0400, Jeff a écrit : Could you give detail on how you mesured those 15 seconds ? Is that using a gutsy CD or on an installed version? GNOME should take less than 10 seconds to start on a such configuration </PRE> </BLOCKQUOTE> This is measured using a stopwatch (my simple wrist watch), on a fully installed and up-to-date ubuntu gutsy desktop using gnome. Compiz is not enabled (because it eats 15 secs login time too!). My session started items are: <UL> <LI>the system-config-printing notification area icon <LI>gnome power manager <LI>gnome volume manager <LI>network manager <LI>tracker (however, I set it to start only after 50 seconds; and I "feel" it starting [scratching the drive] waaaay after the desktop is loaded, deskbar or not) <LI>update notifier </UL> My panel was, at the moment of that test, pretty clean (and did not change between iterations). From what I remember, it had: <UL> <LI>gnome menu bar <LI>window list applet <LI>notification area <LI>4 launchers <LI>sensors-applet </UL> To make the benchmark somewhat rigorous, I make a cold start (that means powering off the machine entirely) between the two tries. Starting with the deskbar applet vs starting without that applet on my panel makes a 15 seconds difference. Where is my federico-promised 3 seconds gnome login time :) ? Here is what I consider "loaded" and what I consider "not ready": <UL> <LI>all panel applets must be loaded <LI>desktop must be loaded (in my case, I don't even have nautilus drawing the desktop so...) <LI>the hard drive LED must have stopped flashing (it must be *off*) </UL> Unless there were some very serious performance optimizations between deskbar 2.19.92 and 2.20, I would believe that my 13-15 seconds (approximative) login time difference still applies. Also, my laptop is not using autologin, so I start my stopwatch at the *precise* moment when I hit the "enter" key after entering the password. That is my starting point in order to be somewhat methodical, otherwise you can't have any precision with autologin (I think). </BODY> </HTML>