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 …
-
-
If you would like a testbed for experimenting with this on Windows, I have one posted on github that you can use. I would like to add RIORegisterBuffer() but haven't gotten around to it:https://github.com/cmuratori/largepages …
-
Note tangentially that if you are running a server, you can optionally just use 2mb pages, which are always locked to physical memory by default. This is not a viable way to ship an application to consumers, but "in the cloud" you could do it, and it probably the best option.
- 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.