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 …
-
-
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.
-
Finally, if you use RIORegisterBuffer() and it helps, be sure to thank
@mmozeiko, who I believe is the person who suggested it to me. Never would have thought about it as an option otherwise. - Show replies
New conversation -
-
-
In the Discussion section of the readme, you say the test is less about small vs large pages than demand-driven vs upfront provisioning. That seems inconsistent with the --rio results (which is ~5% net faster for me but as expected shifts the time from writing to VirtualAlloc).
-
That is, the --rio results suggest that almost all of the 10x net win for --large is indeed coming from the large page advantage rather than the incidental upfront provisioning you also get with large pages, no?
- 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.