Thanks Jacob!
On 16 October 2015 at 13:56, Jakob Kummerow wrote:
> It's not about what the "internal array representation" is, it's about how
> the array is accessed. V8 employs all sorts of smarts to make JavaScript
> execution very fast, because that's its job. Accessing things via the C++
> A
It's not about what the "internal array representation" is, it's about how
the array is accessed. V8 employs all sorts of smarts to make JavaScript
execution very fast, because that's its job. Accessing things via the C++
API ("array->Set(...)" in your example) isn't anywhere near as optimized.
The
Hello everyone,
I've noticed peculiar performance characteristics of V8 objects when
benchmarking my V8-embedding application. In particular, v8::Array is
incredibly expensive - each Set(index, value) operation on an array
consistently takes 100ns on a 3.4Ghz Xeon, instead of single digit
nano
Hi,
I am having build issues on Windows (10). I have followed the instructions
at https://chromium.googlesource.com/v8/v8/+/master/docs/building_with_gyp.md
and managed to generate a project (using build/byp_vp
-Dcomponent=shared_library) and open it in Visual Studio (2015) without
problem.
H
