FC2: gnome-terminal takes much longer to startup than Mozilla

[Will Cohen]

Yusuf Goolamabbas wrote:
> On Fri, May 21, 2004 at 07:14:42PM +0300, Panu Matilainen wrote:
> 
>>On Fri, 21 May 2004, Colin Walters wrote:
>>
>>
>>>My suspicion is that you have something crazy in your shell init files
>>>(e.g. ~/.bashrc).
>>
>>...or there's something wrong with DNS - all Gnome (and KDE for that 
>>matter) applications take AGES to start if DNS is failing.
> 
> 
> Forgot to mention that I did the test immediately after a fresh install
> so if there is something crazy in the shell init files, it wasn't added
> by me
> 
> DNS works since I can browse the web using Mozilla
> 
> During install, I enabled the firewall and allowed ssh in
> 
> Regards, /yg

I am working on tools and techniques to better measure the performance 
of desktop applications with the goal of improving performance of 
desktop applications. xterm would certainly be considered in the 
desktop. Could you do the fill out the following information and post 
the results of these simple experiments?

These are still pretty rough procedures, but it will give us some ideas 
where to look.



What is the hardware configuration of the system:

Processor (output of /proc/cpuinfo):
Memory:
Harddisk drive:
Video card:

What is the software configuration of the system:

kernel being used (uname -r):
rpm versions of packages (rpm -qf `which xterm`):

In each case you will need to exit the newly started xterm once it has 
started.

What is the output of:

/usr/bin/time xterm


What is the output of (note that the output is going to be split
between the current xterm and the new xterm:

LD_DEBUG=statistics xterm


Also get a memory map of the xterm:

xterm &
# will print out pid of background process. use the number below
cat /proc/2201/maps > /tmp/xterm_maps

As root run oprofile to find out which executables and libraries are 
being used:

opcontrol --setup --vmlinux=/boot/vmlinux-`uname -r` --separate=library
opcontrol --reset; opcontrol --start; xterm; opcontrol --shutdown
opreport

If there is a complaint about opcontrol not being able to find the 
kernel image, replace "--vmlinux=/boot/vmlinux-`uname -r`" with 
"--no-vmlinux".

-Will