awsm-web VS scheduler-test

I wrote an opinionated WebGL wrapper in Rust/WASM here: https://github.com/dakom/awsm-web

The idea is that it does more cacheing of things like uniform locations and such so you do very fast in-memory lookups in WASM without hitting the JS Api as much.

In the future this will be obsolete since WebGPU has a more optimal API to begin with, and Rust/WASM won't need to go through the JS layer due to "interface types"

this is the test you are referring to: https://github.com/drcmda/scheduler-test it tested against severe stress. the cubes had artifical runtime delay, which would clog the main thread. the github repo now contains a vanilla test that you can run, it will block your cpu for 1-2 seconds. this is repeated every 2 seconds. a vanilla app trying to get through this will consequently go to its knees, but react can schedule it away.

this btw, as absurd as it may seem to you, is a react feature. the upcoming react 18 release is pretty much based on it.

this is complete bs though, he merely removed the stress from the stress-test, the very thing it's testing against. the updated test is here: https://github.com/drcmda/scheduler-test it includes the stress test (500 instances of text geometry), re-created every 2 sec. simply creating them takes 1-2 seconds. svelte, like everything else is going to choke on this. react on the other hand can balance load.