Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Investigate GPU rasterization #3787

Closed
nathansobo opened this issue Oct 10, 2014 · 20 comments
Closed

Investigate GPU rasterization #3787

nathansobo opened this issue Oct 10, 2014 · 20 comments

Comments

@nathansobo
Copy link
Contributor

I've been following the Chromium graphics discussion list and they've been talking about GPU accelerated rasterization. Curious if this is something we can enable in Atom (if it isn't already) and what the benefits would be.

http://www.chromium.org/developers/design-documents/chromium-graphics/how-to-get-gpu-rasterization

/cc @zcbenz

@zcbenz
Copy link
Contributor

zcbenz commented Oct 23, 2014

Currently it is only enabled on Android > 4.4.3, there is a --force-gpu-rasterization flag but only available on Android too. After some searches in the issues list I think it is just not ready on other platforms.

@nathansobo
Copy link
Contributor Author

Thanks for checking that out.

@nstepien
Copy link

You can enable this on the desktop too in Canary via chrome://flags/#enable-gpu-rasterization
I think this is worth another investigation.

@nathansobo
Copy link
Contributor Author

@MayhemYDG I just checked it out in Chrome 40 and at least on OS X it's not available:

screenshot 2015-01-25 07 08 42

@nstepien
Copy link

That's why I specifically mentioned "in Canary".

@nathansobo
Copy link
Contributor Author

@MayhemYDG Oh sorry I missed that!

@nstepien
Copy link

nstepien commented Apr 1, 2015

So now that Atom is on Chrome 41, can we access flags somehow to enable gpu rasterization?

@postcasio
Copy link
Contributor

You can start atom with atom --force-gpu-rasterization to enable it.

@YurySolovyov
Copy link

not sure if that placebo effect, but it seems to work smoother, probably need to profile to be sure.

@kevinsawicki
Copy link
Contributor

@nathansobo is this still something to investigate or can this be closed?

@nathansobo
Copy link
Contributor Author

@zcbenz Is this enabled by default now? It's unclear to me whether options that are enabled by default in Chrome need to be explicitly enabled in Electron.

@simurai
Copy link
Contributor

simurai commented Jul 29, 2015

Followed the steps here.

screen shot 2015-07-29 at 11 47 40 am

So in my case it's "off (device) - not supported on the device". I'm on a MBP (Retina, 13-inch, Late 2012)

@nathansobo
Copy link
Contributor Author

As soon as @zcbenz can confirm that there's nothing more to do to enable GPU rasterization when it's supported on the underlying platform, I'm happy to close this. Until then, I personally would like to keep it open as a reminder.

@anaisbetts
Copy link
Contributor

You can check this with the following code:

bw = require('remote').require('browser-window')
b = new bw({width:500, height: 500})
b.loadUrl('chrome://gpu')

Whether it's on or not depends on all kinds of factors - we actually explicitly force GPU rasterization in the Slack app because it makes a difference on OS X

@limoragni
Copy link

If you are lazy like me you can go to the console and use window.location.href = "chrome://gpu/" to load the GPU info screen. I have a Macbook Pro mid 2015 and have it disabled. Any ideas why? Is there any downsides on explicitly forcing GPU rasterization? Would I benefit from this when using video and svg?

@YurySolovyov
Copy link

@limoragni it should print reasons of disabling features a little below (shot from Chrome, not Atom)
image

@limoragni
Copy link

@YurySolovyov The reason is the same than you screenshot. It says that its disabled by command line or about:flags. Isn't supposed to be enabled by default?

@YurySolovyov
Copy link

@limoragni maybe file a bug to chrome then?

@lock
Copy link

lock bot commented Mar 30, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked and limited conversation to collaborators Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants