On Wed, Apr 08, 2015 at 12:37:23PM +1000, Peter Ross wrote:
In my experience with fbcon, large output (e.g. dmesg or cat /var/log/syslog) will slow the entire system noticably, but switching to another vt (Ctrl+Alt+F2) "fixes" it.
I also noticed it running scren inside xterm, but it was MUCH MUCH MUCH faster to recover -- it's the main reason I start X by default these days.
Until now I have not seen it inside xterm.
It seems to be the terminal application itself, konsole or gnome-terminal, which holds all terminals in one application.
It means, KDE's konsole becomes unresponsive. I can switch to IceWeazel (e.g.) but the drawing of another konsole window takes a long long time.
xterm is much faster than gnome-terminal (or anything else that depends on libvte)...that's mostly because libvte is horribly slow (partly because it does more complicated things, like unicode) e.g. try running 'time ls -lR /' in xterm, gnome-terminal, and konsole. xterm will finish much faster than the other two. mrxvt (my previous favourite terminal) is also much faster than any libvte-based terminal, about as fast as plain old xterm. unfortunately, it doesn't support unicode so i finally gave up using it a couple of years ago (i switched to roxterm which is, IMO, the least crappy of the libvte-based terminals - i tried them all when i reluctantly accepted that i'd have to give up mrxvt) i have no idea about Konsole because I don't use it...but i suspect that if it does fancy modern stuff like unicode then it's probably also slow like libvte. craig -- craig sanders <cas@taz.net.au>