Benchmarking dependencies about benchmarking

[mhdawson]

If I understand correctly the point is that we should be tracking the benchmarks for the javascript engine as well. For example, running the octane benchmarks regularly. That makes sense to me as we already do that internally at IBM as one measure of performance between releases.

[trevnorris]

I fully support adding these to the benchmark list, but these don't address the "call to native".

These would probably have to be custom written, as there are no benchmarks I'm aware of that track things like JS -> native and back again. One thing we've noticed in V8 is that Object::Set() is very slow. To the point that if more than 2 values need to be set it's faster to pass those values to JS and set them there.

Benchmarks addressing that would also be interesting to track across implementation. Though would require writing native modules to achieve.

[obastemur]

These would probably have to be custom written, as there are no benchmarks I'm aware of that track things like JS -> native and back again.

@trevnorris How about preparing the benchmark for those with upcoming node.js API ?

[trevnorris]

@obastemur I can put that on my list, but not sure how soon I can get to it. It would be helpful if there was a list of specifics we'd want to test for in this regard.

[mhdawson]

This issue is > 2 years since the last conversation. Going to close. Please feel free to re-open.