Vivaldi Helper Requires High Performance GPU
apocryphal last edited by
I just noticed by way of the excellent gfxCardStatus program, that Vivaldi is forcing my MacBook Pro to use its power-hungry discrete GPU instead of the energy saving integrated Intel GPU.
Activity Monitor shows that the process "Vivaldi Helper" requires a high performance GPU. This doesn't seem like it should be the case and is probably a bug.
Vivaldi should probably also support App Nap (which can further reduce power consumption) like Chrome and Safari are able to.
luetage last edited by luetage
Hmm, try and untick the chrome setting "use hardware acceleration when available" and see what happens.
You can get there by visiting chrome://settings/ and clicking "show advanced settings". This will of course disable all hardware acceleration, at which point your cpu does the job....
... and don't forget that the change won't take effect until you restart Vivaldi. When you do, go into "Tools / Task Manager" and you'll see that the GPU Process helper is no longer active.
FYI, here's what's going on in that GPU Process:
Chromium-based browsers use the GPU to accelerate compositing and it's (typically) more efficient and better in terms of performance than using the CPU because the GPU is designed for these types of workloads. You'll have to profile your system to see if disabling hardware acceleration really gives you a net benefit.
One more thing... vivaldi://gpu will give you some additional information should you try switching to the integrated GPU and compare its capabilities to the discrete GPU.
While I don't dispute the point you were trying to make in your initial post, I don't think that using the discrete GPU is a bug given that it's available for use. Some features might not be available on the integrated GPU either (arguably) making the discrete GPU a better choice.
Best of luck with your testing.
reach3r last edited by
So this is still a thing.
I love Vivaldi, but this is driving me nuts. Whenever I disconnect my MBP from the external Display (which requires the dedicated GPU to be used) Vivaldi is the primary offender that prevents the GPU from being switched over to the integrated GPU.
And my research so far has not shown any reason why this would be. For the GPU acceleration purposes that the browser requires even the very basic Intel iGPU is plenty.
This makes Vivaldi just short of agonizing and unusable for any sort of mobile work. The Macbook Pro I am working with (15" mid 2015, dedicated GPU) has quite OK battery life on the iGPU, but with the dedicated GPU it drops to half or even a third of that, rendering any mobile work longer than 90-120 minutes impossible without the power supply.
While that last part is not the fault of the Vivaldi devs, they could damn well make sure they don't use the inefficient way to handle things.
fuorviatos last edited by
yeah - I’m fully seconding you on this. My MacBook just runs out of the battery quicker when the dedicated gpu is active. This is the case only for Vivaldi. If it’s not a bug I am going for a neglected feature. Can we report this to the devs team?
I’m gonna try to switch off the accelaerarion and see where it gets me since I don’t really watch video content in Vivaldi it may work...
I will let you know guys.
ryofurue last edited by
@fuorviatos: I recommend filing a bug report. Despite the name, you can submit a feature request, too.