Replies: 2 comments
-
Thank you for the reference. Obviously I'll study it to understand if it can be leveraged in the project. If this approach is applicable to this extension, it should be applied in a systemic way — clearly it is not as a singular issue. So I am converting it to a discussion. |
Beta Was this translation helpful? Give feedback.
-
Is it supported by Right now the addon structure is simple: everything is in C++. It practically has no JS. JS started to appear only for advanced features not directly/properly supported by All methods follow more-or-less the same pattern: decoding parameters from JS to C++ structures, calling the underlying library (RE2), decoding results creating the necessary JS structures. Only the last step involves any JS object creation/memory manipulation. Current all of the above are done in C++. As soon as we are in C++ all internal calls are “fast”. My understanding is that we can shift the JS/C++ boundary somehow keeping more logic in JS making “fast” calls to C++ for an advanced functionality. Is this the idea? I appreciate any advice on that topics. The Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
https://www.yagiz.co/using-v8-fast-api-in-node-js-core/
V8 Fast API removes a lot of the overhead of calling into C++
Beta Was this translation helpful? Give feedback.
All reactions