Thread replies: 7
Thread images: 1
Thread images: 1
Anonymous
Nvidia Optimus laptop: Tales of the primusrun 2017-07-22 03:38:51 Post No. 61500314
[Report] Image search: [Google]
Nvidia Optimus laptop: Tales of the primusrun 2017-07-22 03:38:51 Post No. 61500314
[Report] Image search: [Google]
File: 1495567197868.png (126KB, 309x313px) Image search:
[Google]
126KB, 309x313px
Nvidia Optimus laptop: Tales of the primusrun
Anonymous
2017-07-22 03:38:51
Post No. 61500314
[Report]
>Launch glxgears on iGPU
>Utilization stuck at 75% 7000 FPS
>Launch gears on dGPU
>Util drops to 50% on dGPU 5000 FPS
>Both the dGPU and iGPU can't push more than 7000 FPS independent
>Keep running both and expand the glxgear window on the dGPU
>Util drops on dGPU and iGPU staggers down to 270 FPS with them both running.
What in the fresh hell is this. How does this optimus actually function?
>>
>>61500314
Might be drawcall limited by then, 7000 fps is 0.14ms, 5000 fps is 0.2ms, 270 is 3.7ms
>>
glxgears is not a benchmark.
Test it with unigine valley or something.
>>
>/g/ - Tech Support for nVidiots
>>
>>61500314
Why must you linux tards run something that can't handle advanced hardware management?
Have you ever noticed that Intel Speedstep and AMDs CPU functionality for increasing and decreasing CPU clock depending on workload is garbage in linux?
It's basically done in a statewise matter, rather than dynamically, like under Windows or OSX.
>>
>>61500314
>primusrun
>not optirun
found the problem
>>
>>61501986
not any more
Thread posts: 7
Thread images: 1
Thread images: 1