zlacker

[parent] [thread] 1 comments
1. yazzku+(OP)[view] [source] 2023-08-31 00:19:59
> We recently developed stress test scenarios for rendering complex scenes—like thousands of layers edited by 50 multiplayer users—and took a very deep dive into CPU and GPU profiles.

I don't really know what any of this means. You're running a single-thread graphics API (OpenGL) in a browser (does WASM support background threads?). On any modern PC, that's gonna look like 1 CPU thread doing all the work and the GPU idling 80% of the time waiting for something to happen.

replies(1): >>jilles+Qs
2. jilles+Qs[view] [source] 2023-08-31 05:10:40
>>yazzku+(OP)
> does WASM support background threads?

yes

Figma is able to use more than 1 CPU core and also claim a lot of your GPUs capabilities.

Don't believe me? Open Figma, load a large file and watch it use multiple CPU cores using htop. Driving the GPU is not all the application does. It also has to work with a largish model and abstract syntax tree and do lots of complex things with that before it goes anywhere near the GPU and opengl. Driving that probably happens on the main thread.

On a modern M1, the app is fast and responsive. It only uses a few worker threads (less than the number of CPU cores) and the GPU is fast enough to keep framerates high if you do things like zooming and panning the view. It's the older and slower laptops that are going to be more challenging.

[go to top]