After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 89507 - ls -R / consumes my CPU
ls -R / consumes my CPU
Status: RESOLVED DUPLICATE of bug 96879
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: VTE Maintainers
Nalin Dahyabhai
Depends on:
Blocks:
 
 
Reported: 2002-07-31 09:12 UTC by Michael Meeks
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Michael Meeks 2002-07-31 09:12:28 UTC 
VTE performance is dire; both using and not using pango:

this is not limited to highly intensive tasks either, a simple make of
nautilus results in:

  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 1409 michael   16   0 44352  36M  7496 R    55.3 14.5   3:01
gnome-terminal
18857 michael   11   0  4988 4988   764 R     8.9  1.9   0:00 ld
18022 michael    9   0  2228 2228   860 S     5.9  0.8   0:00 sh
Comment 1 Michael Meeks 2002-07-31 09:13:59 UTC 
From my rough profiling the functions chewing the CPU are:

vte_terminal_draw_chars's
        pango_x_render_layout, and
        pango_layout_set_attributes
Comment 2 Nalin Dahyabhai 2002-08-08 02:45:34 UTC 
The input and output routines should be faster now, though I expect
you'd get better performance with Xft than with Pango, which is doing
more processing to render a character than Xft would.  Beyond a
certain point, this is going to be a subjective measure, though.
Comment 3 David Kennedy 2002-11-20 21:31:34 UTC 
I'm collecting "vte is slow" bugs in 96879

*** This bug has been marked as a duplicate of 96879 ***