4 ms·

Awesome achievement, but like most OpenGL bridge techniques, 15fps with artifacts is not usable.

• CyberRabbi 6y ago
  The demos run from the terminal seem to run at a much higher frame rate. Firefox webgl demo slowdown may be due to other factors.
  • aodaki 6y ago
    Right. Frame rate heavily depends on workload. For me, it is completely fine. I just develop some softwares with little graphics load, and use Web applications and watch some videos. You have no luck here if you are going to play modern games, but modern proprietary game engines do not support AArch64 Linux anyway. It would be difficult time for Linux desktop if other PC vendors migrate to AArch64.
    • CyberRabbi 6y ago
      It’s still a really large discrepancy. I would guess something is broken somewhere. What is the webgl frame rate on native Mac? Have you tried running those webgl demos with chromium?
      • aodaki 6y ago
        You can see native Mac demo at: https://www.youtube.com/watch?v=ezvQPREjN1s https://www.youtube.com/watch?v=ezvQPREjN1s Note that I haven't really optimized it yet. Certainly there should be low-hanging fruits, but I don't dare to get them as it is good enough for me as GNOME is no longer laggy and I know some overheads cannot be eliminated. If I have to do graphics-intensive workload, I would simply run it on macOS or buy another accelerator as M1 is not the best performant graphics accelerator in the market anyway.
• coldtea 6y ago
  15fps on the browser? Just fine. Who cares for WebGL performance on the browser for dev work unless he's in that racket? He gets 700fps and close to OpenGL benchmarks he runs...