4 ms·

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.

adamnemecek 9y ago
I’m getting 60 on X. Are you using safari?
- Jyaif 9y ago
  Irrelevant as on iOS Apple does not allow any other rendering engine other than Webkit.
  - pdpi 9y ago
    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.
    - paraboul 9y ago
      This is a shader, there is absolutely no JS code involved. The code runs directly on the GPU
      - pdpi 9y ago
        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.
westoncb 9y ago
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).
- deaddodo 9y ago
  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.
drifkin 9y ago
Make sure Low Power Mode is off, if it's on it'll have a big effect on performance.
- deaddodo 9y ago
  That was it. Didn't even remember that I have it on.
dingo_bat 9y ago
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.
melling 9y ago
I’m getting 60 fps on my iPhone X.
always_good 9y ago
Why wouldn't it be resolution dependent unless you specifically knew otherwise?
- deaddodo 9y ago
  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.

adamnemecek 9y ago

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

Jyaif 9y ago
Irrelevant as on iOS Apple does not allow any other rendering engine other than Webkit.
- pdpi 9y ago
  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.
  - paraboul 9y ago
    This is a shader, there is absolutely no JS code involved. The code runs directly on the GPU
    - pdpi 9y ago
      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.

westoncb 9y ago

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).

deaddodo 9y ago
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.

drifkin 9y ago

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

deaddodo 9y ago
That was it. Didn't even remember that I have it on.

dingo_bat 9y ago

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.

melling 9y ago

I’m getting 60 fps on my iPhone X.

always_good 9y ago

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

deaddodo 9y ago
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.