Bug 504048

Adding to this:

I have a Thinkpad X200 with "Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)"/"Intel Mobile Intel® GM45 Express Chipset"

List below gtkperf results running both KMS and "nomodeset".  The "nomodeset" run is about 15 seconds faster.... (114 vs. 129).

Here are results running gtkperf with KMS boot/1280x1024:

[tbl@tlondon ~]$ gtkperf -c 500 -a
GtkPerf 0.40 - Starting testing: Thu Jun  4 08:24:02 2009

GtkEntry - time:  0.88
GtkComboBox - time:  6.24
GtkComboBoxEntry - time:  4.40
GtkSpinButton - time:  3.57
GtkProgressBar - time:  2.38
GtkToggleButton - time:  2.10
GtkCheckButton - time:  0.65
GtkRadioButton - time:  2.08
GtkTextView - Add text - time: 10.62
GtkTextView - Scroll - time:  6.83
GtkDrawingArea - Lines - time: 25.69
GtkDrawingArea - Circles - time: 45.33
GtkDrawingArea - Text - time: 16.05
GtkDrawingArea - Pixbufs - time:  2.53
 --- 
Total time: 129.37

Quitting..
[tbl@tlondon ~]$

For comparison, here is gtkperf output running with "nomodeset nopat" boot/1280x1024:

[tbl@tlondon ~]$ gtkperf -c 500 -a
GtkPerf 0.40 - Starting testing: Thu Jun  4 06:28:27 2009

GtkEntry - time:  0.87
GtkComboBox - time:  7.17
GtkComboBoxEntry - time:  5.22
GtkSpinButton - time:  3.92
GtkProgressBar - time:  1.73
GtkToggleButton - time:  1.92
GtkCheckButton - time:  0.76
GtkRadioButton - time:  2.15
GtkTextView - Add text - time:  9.18
GtkTextView - Scroll - time:  4.60
GtkDrawingArea - Lines - time: 23.35
GtkDrawingArea - Circles - time: 33.16
GtkDrawingArea - Text - time: 16.75
GtkDrawingArea - Pixbufs - time:  3.46
 --- 
Total time: 114.26

Quitting..

Tom, couldn't we get /var/log/Xorg.0.log, /var/log/dmesg, and (if you have any) /etc/X11/xorg.conf? I am not sure how much helpful it actually is, but just to be sure we are not overlooking anything.

Thank you

Created attachment 346647 [details]
Xorg.0.log booting with "nomodeset nopat"

Sure, I'll attach as requested, starting with Xorg.0.log

Here are requested files for a boot with "nomodeset nopat"/1280x1024 obtained when I ran:

[tbl@tlondon ~]$ gtkperf -c 500 -a
GtkPerf 0.40 - Starting testing: Fri Jun  5 06:14:20 2009

GtkEntry - time:  0.84
GtkComboBox - time:  6.75
GtkComboBoxEntry - time:  5.20
GtkSpinButton - time:  3.89
GtkProgressBar - time:  1.73
GtkToggleButton - time:  1.75
GtkCheckButton - time:  0.80
GtkRadioButton - time:  1.97
GtkTextView - Add text - time:  9.07
GtkTextView - Scroll - time:  4.73
GtkDrawingArea - Lines - time: 27.24
GtkDrawingArea - Circles - time: 36.75
GtkDrawingArea - Text - time: 16.61
GtkDrawingArea - Pixbufs - time:  3.54
 --- 
Total time: 120.88

Quitting..
[tbl@tlondon ~]$

Created attachment 346648 [details]
output of "dmesg" booting with "nomodeset nopat"

Dmesg output

Sorry, forgot to mention: "no xorg.conf".

I'll boot later (with newer monitor) to get Xorg.0.log and "dmesg" booting with KMS.

BTW, "gtkperf" does not seem to run "smoothly" on my box: it appears to hang sometimes during:

GtkComboBox - time: 11.59
GtkComboBoxEntry - time:  8.86

Notice that the previous run reported in #3 above was:

GtkComboBox - time:  6.75
GtkComboBoxEntry - time:  5.20

I've noticed quite a bit of variance here, and curiously, it appears I can affect this by "just moving the mouse".

Sounds like this comment from fedora-test:

On an ECS 945 GCT-M/1333 the X server randomly stalls,
apparently frozen.  However, moving the mouse restores
normal operation, at least for a while.  This happens with
getperf.  It also seems to happen during graphical install.

Anything obvious for me to do to provide more here?

Created attachment 346656 [details]
my Xorg.0.log with intel driver, nomodeset

Created attachment 346658 [details]
my dmesg output, nomodeset

Created attachment 346676 [details]
Xorg.0.log booting with KMS

Here is Xorg.0.log from boot with KMS/1280x1024:

[tbl@tlondon ~]$ time gtkperf -c 500 -a
GtkPerf 0.40 - Starting testing: Fri Jun  5 08:56:36 2009

GtkEntry - time:  0.72
GtkComboBox - time:  6.59
GtkComboBoxEntry - time:  4.58
GtkSpinButton - time:  3.64
GtkProgressBar - time:  2.38
GtkToggleButton - time:  2.19
GtkCheckButton - time:  0.62
GtkRadioButton - time:  2.01
GtkTextView - Add text - time: 11.47
GtkTextView - Scroll - time:  6.43
GtkDrawingArea - Lines - time: 25.90
GtkDrawingArea - Circles - time: 42.13
GtkDrawingArea - Text - time: 14.65
GtkDrawingArea - Pixbufs - time:  2.44
 --- 
Total time: 125.76

Quitting..

real	2m6.096s
user	0m15.734s
sys	0m0.591s
[tbl@tlondon ~]$

Created attachment 346677 [details]
dmesg output from "gtkperf" run booting with KMS

Created attachment 347371 [details]
X.org.log from 82865G F10 Compaq Evo D300

I'm also experiencing very poor performance on my Compaq Evo D300 with 82865G on a F10 system. (X.org.log attached above, id=347371). Everything's painfully slow compared to my previous Mandriva installation, scrolling minimizing, moving etc.

Here's my gtkperf:

intel driver 1680x1050
GtkEntry - time:  0.66
GtkComboBox - time:  5.56
GtkComboBoxEntry - time:  4.03
GtkSpinButton - time:  1.66
GtkProgressBar - time:  1.02
GtkToggleButton - time:  1.45
GtkCheckButton - time:  0.57
GtkRadioButton - time:  1.30
GtkTextView - Add text - time:  5.99
GtkTextView - Scroll - time:  3.81
GtkDrawingArea - Lines - time:  2.47
GtkDrawingArea - Circles - time:  2.74
GtkDrawingArea - Text - time: 20.31
GtkDrawingArea - Pixbufs - time:  1.14
 --- 
Total time: 52.73

On my 965GM laptop, the vesa driver is also faster, though not as dramatically.  Total times are nomodeset/vesa ~5.3, KMS/UXA ~11, nomodeset/EXA ~14.

Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

I have been running rawhide and the performance problem has not been
resolved as of last week.  At that time, I finally had enough of
the poor performance of the intel driver and talked my boss into
updating my desktop.  I still have the old desktop kicking around, but
it's a hassle for me to test anything on it now.  Let me know if something
has been changed in the last week that might have improved the performance
and I'll test for you.  Otherwise, the intel driver in rawhide is just
as slow as ever.  About 10x slower running gtkperf than my current
desktop that has comparable specs but ATI graphics.  As far as I'm
concerned, you can close this bug if you want.  I'll never use another
Intel graphics chip with Linux.

I am sorry to hear it. Don't worry about this bug, somebody else will hit and we can fix the bug with her.

Closing as INSUFFICIENT_DATA

What more data are you looking for?  He said the new driver is still just as slow.

(In reply to comment #19)
> What more data are you looking for?  He said the new driver is still just as
> slow.  

a) the truth is that we are now more concerned with making KMS drivers working at all, so this will take some time before fixing speed will get enough attention from developers, I am afraid,
b) yes, you are right, reopening and making blocking "Intel is slow bug".

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Created attachment 378727 [details]
dmesg for compaq d530sff 

Horrid performance here too, in the range of seconds-per-line of scrolling in firefox.

Created attachment 378728 [details]
Xorg.0.log for same machine

[spider@kokong ~]$ gtkperf -c 500 -a
(gtkperf:2828): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(gtkperf:2828): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
GtkPerf 0.40 - Starting testing: Wed Dec 16 11:30:32 2009

GtkEntry - time:  0.48
GtkComboBox - time: 12.53
GtkComboBoxEntry - time:  7.04
GtkSpinButton - time:  2.79
GtkProgressBar - time:  2.48
GtkToggleButton - time:  2.03
GtkCheckButton - time:  1.63
GtkRadioButton - time:  2.19
GtkTextView - Add text - time: 26.22
GtkTextView - Scroll - time:  3.35
GtkDrawingArea - Lines - time:  7.72
GtkDrawingArea - Circles - time: 23.02
GtkDrawingArea - Text - time:  6.16
GtkDrawingArea - Pixbufs - time:  0.69
 --- 
Total time: 98.33

Quitting..

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.