One of the Unity developers raised some important points about WASM's memory model in a github thread. I contributed some additional thoughts here:https://github.com/WebAssembly/design/issues/1397#issuecomment-926119051 …
-
-
The obvious one is VirtualLock(). In my (limited) testing, it does not improve the performance substantially.
-
The non-obvious one is RIORegisterBuffer(). Although I didn't know about it last time I tested these things, it is apparently much faster. So my _assumption_ would be, if someone was going to try this on Windows, they would want to use RIORegisterBuffer().
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.