[v8-users] Re: GC cost of adding to an object with 50,000+ keys

I switched to a Map which looks like it may have solved the issue. See this: https://jsperf.com/es6-map-vs-object-properties/ And, running Node.js --perf with the code from that jsperf yields the following (on Node v8.9.1 which, according to process.versions, is V8 6.1.534.47): *Map (15.7% in

Re: [v8-users] How to build a fixed version of V8 and its dependencies.

The depot_tools system makes this easy, actually: git checkout gclient sync ninja -C out/ d8 (If you go back far enough before ninja was supported, replace the last command with the equivalent make/GYP based build.) On Mon, Nov 27, 2017 at 9:23 AM Edd Barrett wrote: > Hi

Re: [v8-users] How to build a fixed version of V8 and its dependencies.

Hi Mathias, Thanks for your swift response. On Monday, November 27, 2017 at 1:40:05 PM UTC, Mathias Bynens wrote: > > This is not a direct answer to your question, but we already host prebuilt > `d8` binaries for Linux on 32-bit and 64-bit architectures. We plan on > doing the same for other

Re: [v8-users] How to build a fixed version of V8 and its dependencies.

This is not a direct answer to your question, but we already host prebuilt `d8` binaries for Linux on 32-bit and 64-bit architectures. We plan on doing the same for other operating systems: https://bugs.chromium.org/p/v8/issues/detail?id=5918 By using a precompiled binary, you could bypass

[v8-users] How to build a fixed version of V8 and its dependencies.

Hi, I raised this as a bug, but was asked to re-post here. For a benchmarking experiment I need to build a frozen version of V8. For most VMs this means just checking out a specific git version of the code and building it. For V8 it is complicated by the depot_tools system. I've yet to find a