I don't really understand what's the difference between AAA game and Google Chrome? I thought that modern applications heavily use GPU acceleration. Is it some subset of GPU commands that's required for desktop, compared to AAA game? Is it possible that Google Chrome will crash the OS with some tricky CSS animation (may be in the future version)?
Anyone who's worked in the video game industry knows how insanely inconsistent compatibility can be on across different device configurations. With browsers using more and more GPU acceleration, it wouldn't surprising if some configurations have major performance bugs. The one thing with Chrome is that it has very good compatibility.
However I am going to argue one thing that was mentioned in the article. Chrome is not just about being fast. Its fast executing, fast updating (patching vulns and keeping up pace), more extensible than IE (at least easier to get extensions), sandboxed and significantly more secure than ie , and a way for google to push some good technologies out. Its also cross platform, so any computer I go to I can run chrome on, ie is windows Vista/7 only not even XP which chrome runs on.
I also feel is a good thing that video card vendors will get a swift kick in the balls to get their act together and make their drivers secure and decent finally. Though I cringe at the thought of what the state of webgl will be on linux with ATI drivers.
I don't really get why Chrome is so exciting. OK, it uses the GPU to render pages. That's fine, but that's never the bottleneck for me; my CPU is done rendering pages long before it gets the next byte from the painfully-slow web app that I'm connected to.
What we really need is GPU acceleration for Arc...
By default, google disables hardware acceleration for chrome on a large percentage of linux. As well, Ive never had it work well with open source graphics drivers or new products like wayland. And the desktop integration comes nowhere near firefox
I prefer using Firefox anyway, but if you want to dig deeper regarding your Chrome GPU acceleration you might find the following pages valuable:
chrome://gpu/ -- here you can see the current status of your GPU Acceleration
chrome://flags/ -- search for 'GPU' or 'accel'. This is the place where you can override some related settings, but be aware, that this might break your browser, so better backup your browser configuration directory before changing anything ;-)
just two cents here, as far as I know, all browsers need GPU acceleration.
you can try to turn it off see how fast you can browse.
so without OS, how can browser drive GPU?
The only thing that holds me back from running my Gnome DE in Wayand is that as of version 88 Google Chrome now supports hardware acceleration. But only for X11.
I disagree, only on the grounds that Chrome will max out the tiny GPU in that machine when HTML5 videos or CSS3 animations play. Even simple video effects like Expose will stutter. It's a great machine, but the video card is much too weak for the pixels it has to push. Take it with a grain of salt, of course.
I'm also running the latest Chrome on Linux, on a cheap laptop (although it does have 2 cores). I could run it with no problems and no visible system slowdown.
I guess it also depends on the software used, on drivers, etc ... the technology is very new and still a work in progress.
by design, cannot approach the performance of Direct3D
Yeah, Chrome is not fully hardware accelerated yet and I don't think it will be until at least v11. In a recent test by DownloadSquad it seems they are the ones behind the most in this, even behind Opera. I don't know why they missed this opportunity and didn't give it a higher priority. It's the same problem with hardware acceleration on Android all over again.
It's almost like Google and anything graphics related don't mix, even though improving full hardware acceleration performance is probably as important for the further development of the web as improving Javascript performance was. I think this will be where the new battle between browsers will be in 2011 and 2012 at least.
Performance is heavily bound by the GPU on my system - Chrome goes from sucking up 60% of my CPU down to just 7% when I launch the demo(OK, I've got crappy Intel integrated graphics, but still). I consider that to be a good demonstration that JavaScript performance is now capable of driving detailed 3D scenes.
Actually Chrome on Linux doesn't use hardware acceleration for video playback and never did, while the most recent Firefox almost does, if one turns a couple of experimental knobs.
Not entirely relevant, but it seems like the author is using windows 7 with an old build of chrome. Is there a reason for this? Maybe testing on an old PC to easily spot performance problems? Yet the readme mentions a Nvidia 3080ti gpu, which is quite new.
Meh, I typically use Chrome through a virtual machine with Spice which has broken OpenGL support, so I wasn't getting hardware acceleration anyway. I still get screen tearing in Firefox, for Christ's sake.
Chrome's GPU sandboxing is more aggressive, so it's probably performing extra copies. GPU round-trips (think synchronous operations like 'copy the result from the GPU back to CPU memory) also end up being slower due to the delays introduced by bouncing things between the page and the GPU sandbox.
reply