I run Davinci resolve using optirun on my optimus Thinkpad P52. Recently it started to slow down after 5-10 minutes of work. This doesn't happen when I run resolve when my entire system is using Nvidia Quadro 2000 as the primary GPU (Intel GPU switched off in BIOS). I tried to run glxspheres64 to see if I observe the same behaviour. I do. After a while, the output of glxspheres shows: 435.733893 frames/sec - 486.279025 Mpixels/sec 420.903613 frames/sec - 469.728432 Mpixels/sec 428.335786 frames/sec - 478.022737 Mpixels/sec 452.346389 frames/sec - 504.818570 Mpixels/sec 454.919522 frames/sec - 507.690186 Mpixels/sec 447.317577 frames/sec - 499.206416 Mpixels/sec 441.948527 frames/sec - 493.214557 Mpixels/sec 454.452814 frames/sec - 507.169340 Mpixels/sec 440.717190 frames/sec - 491.840384 Mpixels/sec 422.933600 frames/sec - 471.993898 Mpixels/sec 410.380339 frames/sec - 457.984458 Mpixels/sec 449.037773 frames/sec - 501.126155 Mpixels/sec 138.984963 frames/sec - 155.107219 Mpixels/sec 0.999772 frames/sec - 1.115746 Mpixels/sec 0.999913 frames/sec - 1.115903 Mpixels/sec 1.000030 frames/sec - 1.116033 Mpixels/sec 1.000289 frames/sec - 1.116322 Mpixels/sec 0.999934 frames/sec - 1.115926 Mpixels/sec 0.999885 frames/sec - 1.115872 Mpixels/sec 1.000147 frames/sec - 1.116164 Mpixels/sec 0.999826 frames/sec - 1.115805 Mpixels/sec 1.000129 frames/sec - 1.116144 Mpixels/sec 0.999662 frames/sec - 1.115623 Mpixels/sec 0.999982 frames/sec - 1.115980 Mpixels/sec 1.000167 frames/sec - 1.116186 Mpixels/sec 0.999929 frames/sec - 1.115920 Mpixels/sec 0.999882 frames/sec - 1.115869 Mpixels/sec If I use intel-virtual-output to engage the DP and HDMI outputs of my thinkpad, I also notice that after a while the external display starts to refresh at 1 fps whatever app I put to it. This is my bumblebee conf file: # Configuration file for Bumblebee. Values should **not** be put between quotes ## Server options. Any change made in this section will need a server restart # to take effect. [bumblebeed] # The secondary Xorg server DISPLAY number VirtualDisplay=:8 # Should the unused Xorg server be kept running? Set this to true if waiting # for X to be ready is too long and don't need power management at all. KeepUnusedXServer=false # The name of the Bumbleblee server group name (GID name) ServerGroup=bumblebee # Card power state at exit. Set to false if the card shoud be ON when Bumblebee # server exits. TurnCardOffAtExit=true # The default behavior of '-f' option on optirun. If set to "true", '-f' will # be ignored. NoEcoModeOverride=false # The Driver used by Bumblebee server. If this value is not set (or empty), # auto-detection is performed. The available drivers are nvidia and nouveau # (See also the driver-specific sections below) Driver=nvidia # Directory with a dummy config file to pass as a -configdir to secondary X XorgConfDir=/etc/bumblebee/xorg.conf.d # Xorg binary to run XorgBinary=Xorg ## Client options. Will take effect on the next optirun executed. [optirun] # Acceleration/ rendering bridge, possible values are auto, virtualgl and # primus. #Bridge=auto Bridge=virtualgl # The method used for VirtualGL to transport frames between X servers. # Possible values are proxy, jpeg, rgb, xv and yuv. VGLTransport=proxy # List of paths which are searched for the primus libGL.so.1 when using # the primus bridge #PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus # Should the program run under optirun even if Bumblebee server or nvidia card # is not available? AllowFallbackToIGC=false [driver-nvidia] # Module name to load, defaults to Driver if empty or unset KernelDriver=nvidia PMMethod=auto # colon-separated path to the nvidia libraries LibraryPath=/usr/lib64/opengl/nvidia/lib:/usr/lib32/opengl/nvidia/lib:/usr/lib/opengl/nvidia/lib # comma-separated path of the directory containing nvidia_drv.so and the # default Xorg modules path XorgModulePath=/usr/lib64/opengl/nvidia/lib,/usr/lib64/opengl/nvidia/extensions,/usr/lib64/xorg/modules/drivers,/usr/lib64/xorg/modules XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
