Replies: 1 comment
-
You are asking here about the code of calling from Wasm to JavaScript. This tends to vary a little between browsers, but should be very fast. Especially when you are making calls into WebGL or WebGPU like this I imagine the cost of the graphics API call makes the cost of the Wasm/JS crossing insignificant. Obviously the only what to really know this is to measure of the browser(s) you are targetting. In general I would advise against this type of optimization since its likely to be premature, and also change over time as browsers improve. @kainino0x WDYT? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is the performance of A superior to that of B?
Is that: A involves only one context switch, whereas B requires multiple consecutive context switches?
A:
B:
Beta Was this translation helpful? Give feedback.
All reactions