Architecture
Primitive and Reference Types in Javet
There is a vague boundary between V8 primitive and reference types. In Javet, the definition of primitive is a mixture of both V8 and Java primitive types as a trade-off in design.
Feature | Primitive | Reference |
---|---|---|
Interception | No | Yes |
Memory Copy | Copy by Value | Copy by Reference |
Resource Leak | Not Possible | Possible |
Set to Weak | No | Yes |
Reference typed objects keep memory footprint in V8 + JNI + JVM. All resource will be recycled when close()
is called. That is quite an old school way of managing resource. Javet tries to hide that kind of tedious work from Java applications via try-with-resource.
Please refer to Best Practices for detail.
Engine Pool
V8 Isolate and Context in Javet
Getting started with embedding V8 is an excellent article that explains the concepts, design, insights of V8. In summary:
- An isolate is a VM instance with its own heap.
- A context is an execution environment that allows separate, unrelated, JavaScript applications to run in a single instance of V8.
In Javet, that model is simplified to 1 engine - 1 runtime - 1 isolate - 1 context. In V8Runtime, resetIsolate()
and resetContext()
are both exposed. It is recommended to always use resetContext()
to get a brand new V8 context for the following reasons.
resetContext()
is a much cheaper operation with much better performance.resetContext()
is good enough in terms of getting a brand new V8 context.
Javet Engine Pool
Multiple Javet engines are managed by Javet Engine Pool which works almost the same way as a typical DB connection pool. Javet Engine Pool is thread-safe. However, Javet Engine is NOT thread-safe because it is designed to be single-threaded and lock free for the following reasons.
- V8 isolate and V8 context are single-threaded. Thread context violation results in V8 core dump immediately.
- Javet Engine performs better without locks. Actually, Javet engine only validates current thread ID to minimize the performance overhead.
Please refer to Best Practices for detail.
No comments:
Post a Comment