Javascript engine: v8 8.7 accelerates native calls and expands threading

JavaScript engine: V8 8.7 accelerates native calls and expands threading

Google has version 8.7 the JavaScript engine V8 published. The release brings a syntactic innovation that allows asynchronous monitoring of storage areas in threads. There is a new API to speed up C ++ calls.


The almost C API should improve the interaction between the JavaScript applications and C ++ code running in the engine. According to the V8 team, the JavaScript bindings between the engine and the embedded embedders have proven to be needle ear for performance critical functions.

According to the explanation of the almost C API with the connections to the 2D and 3D graphics acceleration, the original implementation was created. However, she does not meet the performance request of API calls, which are, for example, very hardware. The new API not only knows the POD C ++ types (Plain Old Data), but already the current state of some extended types, and it is prepared for additional assets such as INT64_T or typed array.

The FAST C API creates the internal Struct V8 :: CFunctionInfo, which represents the signatures of callbacks in just the C ++ types. To use the developer first creates a callback with a specific signature and always call the V8 :: CFunction :: Make-Method with the callback to create a suitable instance of the V8 :: CFUNCTION. Then you are working on the V8 :: FunctionTemplate, which is next to the Fast-Api-Regular Callback.

Without blockade

The syntactic assessment for Atomics as often at V8 a planned JavaScript standard: Atomics.Waitasync is a non-blocking variant of Atomics.Wait, which checks a position in an INT32Array to a value. Since the pure atomics.Wait method blocks the program sequence, it is not approved in Main, but the asynchronous variant, however,.

Further details can be found in the V8 blog. The release of the JavaScript engine has beta status, the release of the JavaScript Engine, until the associated Chrome version 87 appears as a stable release. An instructions that developers can access the GIT repository can be found in the V8 documentation. In addition, the current engine is included in the beta to Chrome 87, which provides Google via the Chrome Beta Channel.

Like this post? Please share to your friends:
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: