Bug 985367 - Significant 3D performance regression after upgrading from F18 to F19
Summary: Significant 3D performance regression after upgrading from F18 to F19
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-17 11:05 UTC by Jiri Eischmann
Modified: 2015-02-17 16:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 16:12:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jiri Eischmann 2013-07-17 11:05:08 UTC
Description of problem:
I can see significant performance issues in GNOME Shell animations on Intel Graphics Media Accelerator 4500MHD and Intel HD Graphics 3000. I've also talked to several other users who have Intel cards and they experience the same.
I discussed this with GNOME people and they say there have been no changes in GS animations between F18 and F19. So because it seems to be Intel driver specific, I'm filing the bug against this component.
I also tried different kernels - from 3.8 to 3.11 and no changes.

Version-Release number of selected component (if applicable):
2.21.8

Comment 1 Chris Wilson 2013-07-17 21:57:54 UTC
If you can be quantative, that would help a lot. Perhaps a video recorded by a phone would help demonstrate the issue that you observe.

There are 4 main candidates to check for regressions (and interactions between two or more):

gnome-shell
mesa
xf86-video-intel
linux (kernel).

You've ruled out gnome-shell (but check just to be sure) and tested against the older kernels, which leaves just the ddx and libgl to downgrade and check.

Comment 2 Jim Haynes 2013-08-27 22:24:12 UTC
Please see my comment on bug 946911.  Using old graphics hardware that I
guess doesn't do 3D - I don't even know what 3D graphics is nor why I should
want it - things are fine under F18 with gnome in fallback mode.  After
upgrading to F19 top shows that gnome-shell is running all the time, using
about 33% of the CPU in one case and about half that in another, while on
a similar F18 system I don't see gnome-shell running at all.

Comment 3 Fedora End Of Life 2015-01-09 18:57:59 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-02-17 16:12:29 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


Note You need to log in before you can comment on or make changes to this bug.