Bug 958830 - PyMOL rendering is slow
Summary: PyMOL rendering is slow
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 958828
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-02 13:44 UTC by Michal Domonkos
Modified: 2015-02-17 15:08 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description Michal Domonkos 2013-05-02 13:44:14 UTC
+++ This bug was initially created as a clone of Bug #958828 +++

Description of problem:
Contents of the PyMOL Viewer window is refreshing very slowly (like 1 frame per second at most). Same holds for mouse/keyboard input inside that window. As a result, the application becomes unusable.

The main window with the horizontal menu renders normally.

Both Nouveau and ATI drivers are affected (Intel seems to be fine). I have tested several graphics cards, namely:
nVidia Quadro 310
nVidia Quadro 400
nVidia Quadro 2000
ATI FirePro V4800

The ATI card performed much better in comparison with the other nvidia ones, but still very poor.

This issue came up during Fedora 19 Test Days, where almost all testers reported a "slowness" of PyMOL:
https://fedoraproject.org/wiki/Test_Day:2013-04-24_Nouveau
https://fedoraproject.org/wiki/Test_Day:2013-04-25_Radeon

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.14.0-6.fc19.x86_64
xorg-x11-drv-nouveau-1.0.7-1.fc19.x86_64
xorg-x11-drv-ati-7.1.0-5.20130408git6e74aacc5.fc19.x86_64
kernel-3.9.0-0.rc8.git0.2.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. Run pymol
2. Go to Wizard -> Demo and choose an arbitrary demo
  
Actual results:
Slow animations/responsiveness inside PyMOL Viewer.

Expected results:
Smooth performance.

--- Additional comment from Michal Domonkos on 2013-05-02 09:40:11 EDT ---

Created attachment 742708 [details]
Xorg.0.log

--- Additional comment from Michal Domonkos on 2013-05-02 09:40:38 EDT ---

Created attachment 742709 [details]
dmesg

--- Additional comment from Michal Domonkos on 2013-05-02 09:41:43 EDT ---

Also note the similar bug from Fedora 18:

https://bugzilla.redhat.com/show_bug.cgi?id=861656

Comment 1 Fedora End Of Life 2015-01-09 18:01:30 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 2 Fedora End Of Life 2015-02-17 15:08:16 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.