On Tue, 2004-05-25 at 16:31 -0400, Will Cohen wrote:
Funny, I learned about passing xterm a command to execute from your email. :)
Well that's good to hear. :) The -e switch works with gnome-terminal
too, incidentally.
Remember the our goal is to improve the performance of the Linux Desktop, not to be correct every single time.
True, being correct every single time doesn't hurt either. :)
PS I learned today that gnome actually uses gnome-terminal rather than xterm.
It does, and it definitely could stand some performance improvements. I don't think it's _vastly_ slower than xterm (once it's started), but it does often get in the way.
I think it was Warren who mentioned that he has to minimize gnome-terminal when he's doing a noisy compile otherwise it significantly slows down. That's certainly true for me too (although I just toggle to another tab), but I'm not sure if the real problem is with gnome-terminal, pango, or the underlying font system -- or perhaps at layers even lower than that, like really bad or non-existent Render support in the video driver.
Cheers, Jason.
#! /bin/bash # # Simple test to gather data on where gnome-terminal spends time # This is compilicated by the terminal server model of gnome-terminal. # Using oprofile to get an overall view of what is happening on the system # This is only going to work with kernel that have oprofile support # (Red Hat SMP kernels) OPCONTROL=/usr/bin/opcontrol RESULTS_FILE=cattime $OPCONTROL --deinit $OPCONTROL --reset $OPCONTROL --setup --no-vmlinux --separate=library $OPCONTROL --start /usr/bin/time -o $RESULTS_FILE /bin/cat /home/wcohen/jarg422.txt $OPCONTROL --dump $OPCONTROL --shutdown #Need to do analysis after running the test.