Hacker News Reader

Hacker News

Comment by Keloran | Hacker News Reader

Parent Full thread

Keloran

I’m not sure what I’m more impressed by the shader itself was r the fact that it runs at 60fps on an iPhone 7

View on HN

- Westmere Xeon at 3.33GHz

- Radeon RX 580

- 1440p Resolution

- Linux 4.12 with Mesa 17.3.2

At first I thought the demo was broken entirely or was designed as some stress-test because Chrome churned between 0.6 to 0.9 fps. Never cracked 1.0 (yes, never passing one-point-zero).

Then I opened Firefox and not only ran, but never dropped below 30 fps, mostly hovered between 40 and 50.

This will be chrome being in "3D software rasterizer" mode as it tends to produce artifacts badly when run on those kinds of GPUs with mesa.

- Threadripper 1900x

- Radeon Vega 64

- 4k resolution

- Linux 4.15.4 and Mesa 17.3.5 (Fedora 27)

Firefox locked to 60 fps (is there a way to disable vsync?); Chrome hovering somewhere between 9 and 16 fps.

30fps on my old xperia z3. Very impressed. I'm slowly starting to feel like web 3D on mobile is a thing and not just a happy accident when it works.

Meanwhile I'm on 4 fps on a laptop while pushing the laptop to thermal limits.

That's on Chrome. On FF with same laptop...butter-smooth 60fps with no heat.

Whatever this thing is it definitely doesn't like Chrome.

chrome://gpu I bet it's not using all of them. Open chrome://flags and enable "Override software rendering list" and restart. Then thank me later

Works beautifully in Chrome on my iPhone.

Note that Chrome on an iPhone is still just Safari but with different chrome (no pun intended).

And a solid 5 fps on Chrome on Linux on Haswell, heh.

If you have a nvidia GPU, then it may well be the fault of the latest drivers (390.25), which have been buggy, and it's especially notable under Chrome/Chromium (video/audio stuttering, problems with vsync, general slowness, high CPU usage, etc..).

Arch has a recent thread about it: https://bbs.archlinux.org/viewtopic.php?id=234241

I got solid 60FPS using Firefox Developer Edition on Arch, it would be interesting to see what the issue is for you (might be hardware, I'm running a Vega.)

Between 30 and 50 fps on Firefox 58, on Kubuntu, on a slow-ass Intel Celeron 3205U (1.50ghz) laptop.

Amazing. Just amazing.

Re: Vega — I think it's pretty clearly some sort of software issue — other people are having no trouble with mobile/embedded/iGPU hardware. This machine has an Nvidia GT 610 in it, which isn't high end gaming equipment. But it should be adequate for this demo.

You might wanna try activating the #ignore-gpu-blacklist in chrome://flags

But be aware that it can cause some collateral damage like broken websites (if you have it and it bothers you, you can simply turn the flag off again). For example, with my Haswell Intel GPU I had never any problems, but with my Radeon it results in some strange textures on some website. FF has no problems with neither of them.

Same here, 3 to 5 fps on Chrome and a consistent 60 fps on firefox 58. There's definitely something wrong with Chrome for linux. Try the Stripe docs page https://stripe.com/docs/api#error_handling , same issue. Buttery smooth scrolling on firefox but unusable on Chrome.

Anything under 10fps on a modern machine is almost certainly not benefitting from GPU acceleration.

Unless you try running a demanding AAA game in 8K resolution :D

60 FPS + negligible CPU on Chrome OS with Haswell though, interesting.

Yeah, clearly Haswell (+ my GPU) is capable of much more. Just not being utilized well.

I get ~60 fps on Broadwell Xeon, Xubuntu, Chromium, and a 1060 GPU.

I'm getting 30-60 FPS (depending on the scene) on my iPhone 5s, so even more impressive.

On an LG Power X it doesn't even start, beyond freezing Chrome.

Or a minimum of 26fps on iPhone 5S and mostly higher than 40fps.

Seriously? I'm getting 32-36 on the iPhone X. I don't think it's resolution dependent, so I'm pretty interested in why the performance is so much less.

Fragment shaders (which this is) are quite resolution dependent: they are programs which execute at each pixel, so the input size to the algorithm contained in the shader is essentially equal to the resolution (it's not strictly, since other data can be passed in which the program iterates over—but it is fairly uncommon for shaders to make heavy use of loops or recursion from what I've seen).

I understand that, I'm quite acquainted with 3D programming and shaders. But I was under the impression that they were dependent on the resolution of the renderview, not the device.

It's definitely resolution dependent. On my Galaxy S7, the frame rate is 40-45 when the screen is set to 1080p, and drops to 20fps if I increase the resolution to 1440p.

Make sure Low Power Mode is off, if it's on it'll have a big effect on performance.

That was it. Didn't even remember that I have it on.

Why wouldn't it be resolution dependent unless you specifically knew otherwise?

I understood it to be dependent on the resolution of the renderview, not the device. Perhaps I'm incorrect, but the problem in this case was low power mode.

I’m getting 60 on X. Are you using safari?

Irrelevant as on iOS Apple does not allow any other rendering engine other than Webkit.

Not sure if it’s still the case, but there were limitations around JS optimisations in webviews outside Safari, so the question might actually be relevant.

This is a shader, there is absolutely no JS code involved. The code runs directly on the GPU

Right. My point was that, given that Apple have historically limited the optimisations available to webviews, it’s not obvious that WebGL would be exempt of similar limitations.

I’m getting 60 fps on my iPhone X.

I am getting 60 on an iPhone 6s

30-35fps on 6S here. Weird.

Edit: 60fps with Low Power Mode off.

Reply on news.ycombinator.com