When I ran the test in d8 (unfortunately I didn't keep the old binaries
around so can't quickly verify) I saw at most a 10% difference between 7.1
vs 7.9.
Is this manifesting somewhere other than in your micro benchmark? Because
this looks to be pretty much the worst case scenario, the function do
This 600x slowdown was inside of arangosh due to pasting - its not there
anymore in the numbers of my previous post - sorry I didn't mention it
explicitely.
However, if you compare the numbers of my previous post, there still is an
offset of ~40% which I'd still call significant?
--
--
v8-u
I managed to get this working by replacing the native Promise object by
executing the following script:
global.Promise = new Proxy(global.Promise, {
construct: function(target, args) {
const origFunc = args[0];
return new target(function(resolve, reject) {
I've built v8's d8 at 7.1, 7.9 and HEAD and 7.1 is a little faster for the
test you posted in your first email, but there's not much in it. Certainly
nothing near the 600x slowdown you had. I wonder if you're setting any
other flags either at runtime or build time?
On Wed, 12 Feb 2020 at 12:28, Wi
Hi,
for the json tests the results are looking really promising (its this ~2MB
sized file:
https://github.com/arangodb/arangodb/tree/devel/js/apps/system/_admin/aardvark/APP
)
However, all the throw tests don't look as good.
`--no-enable-lazy-source-positions` doesn't bring me in the range o
