Problems I met when using fast API calls. *Hit rate:*
Whether Fast API can take effect seems to be related to JIT. The JIT was not triggered in a simple test example for the first 8000 ~ 11000 times. In a complex project, some high-frequency functions should meet the trigger conditions but fail to trigger in the 20-minute test process. *Property functions are not triggered* Tested the getter setter method of x / y of `Vector2`, but failed to trigger the corresponding CFunction in a big loop. *Questions:* 1. How to improve the hit rate? 2. Is it possible to trigger CFunction directly? 3. Fucntioncallback and CFunction need to be provided at the same time. Can I omit the FunctionCallback? 4. Will property callback supportFast API? *other:* Provide a mechanism to store the function address in a JS variable, jump(instruction) directly to the function, and ignore the sandbox mechanism? On Friday, April 1, 2022 at 10:45:32 AM UTC+8 Patric Lemo wrote: > I know the FastAPI, but it's not fast enough. Is there any way to call the > C functions directly, only considering the case of no parameter and no > return value? For example, you can store the function address in a BigInt > and then invoke it directly in JS. Are there any risks here? Can it be > achieved? > I wonder if anyone knows any other ways to speed up native calls > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/ec630bd1-2466-442d-b315-da7104efc52dn%40googlegroups.com.
