I have created a graph of a login to gnome in hardy using the method described here: http://www.gnome.org/~federico/news-2008-02.html
I have applied the patch there to the ubuntu version of gnome-panel (I have actually dropped ubuntu patch 16_* because I was to lazy to have a look why that patch could not be applied to the instrumented source).
I have done the profiling using a freshly created user and I have created the graph during the second login to that users profile. I have stopped shortly after I had a usable gnome-terminal after about 60 seconds.
Looks like there is something strange going on with pulseaudio and esd at the beginning of startup. Compiz wastes a large amount of time finding out the current configuration using glxinfo and nvidia-settings. There are lots of top_panel size requests, I have not yet looked what that means exactly, though. It would also be interesting to know what happens at second 26 - apt-cache and modinfo take a huge amount of time there which is probably not needed at that point of time. I don't know how useful this is, but perhaps someone gets an idea.
I have created a graph of a login to gnome in hardy using the method described here: www.gnome. org/~federico/ news-2008- 02.html
http://
I have applied the patch there to the ubuntu version of gnome-panel (I have actually dropped ubuntu patch 16_* because I was to lazy to have a look why that patch could not be applied to the instrumented source).
I have done the profiling using a freshly created user and I have created the graph during the second login to that users profile. I have stopped shortly after I had a usable gnome-terminal after about 60 seconds.
Looks like there is something strange going on with pulseaudio and esd at the beginning of startup. Compiz wastes a large amount of time finding out the current configuration using glxinfo and nvidia-settings. There are lots of top_panel size requests, I have not yet looked what that means exactly, though. It would also be interesting to know what happens at second 26 - apt-cache and modinfo take a huge amount of time there which is probably not needed at that point of time. I don't know how useful this is, but perhaps someone gets an idea.