Why the New V8 Is So Damn Fast

Re:Why the New V8 Is So Damn Fast by lovelle on Monday July 30, 2018 @07:12PM (#17649043)

I would insanely choose ruby rather than javascript for the major advantages that has to offer. Performance in most of cases is not a real needed over consistency. Also Ruby 2.6 has jit, would be great to see some bench tests. :P

[ Parent | on HN ]

Re:Why the New V8 Is So Damn Fast by abhorrence on Monday July 30, 2018 @07:20PM (#17649108)

2.6’s JIT is entirely at the method level currently, and unfortunately for certain types of workloads (e.g. Rails) this means the performance benefit is largely outweighed by the call counters and deoptimization checks on every method invocation.

There’s definitely room for improvement, and the inclusion of JIT infrastructure is awesome, it’s just not making much of a performance impact. Yet.

[ Parent | on HN ]

Re:Why the New V8 Is So Damn Fast by jashmatthews on Tuesday July 31, 2018 @08:31AM (#17652612)

The overheads from the call counters and deoptimization checks are tiny. The real problem is that right now MJIT doesn't allow much optimization beyond generating native code equivalent to simply executing the instructions. It's ridiculously simple compared to V8.

[ Parent | on HN ]

Re:Why the New V8 Is So Damn Fast by munificent on Monday July 30, 2018 @07:38PM (#17649241)

V8 is also a method-based JIT as far as I know.

[ Parent | on HN ]

Re:Why the New V8 Is So Damn Fast by tlrobinson on Tuesday July 31, 2018 @12:45AM (#17650597)

Out of curiosity, what are the major advantages Ruby has to offer over JavaScript?

[ Parent | on HN ]

Re:Why the New V8 Is So Damn Fast by windows_tips on Monday July 30, 2018 @07:25PM (#17649138)

Isn't there a Ruby->JS transpiler?

[ Parent | on HN ]

Re:Why the New V8 Is So Damn Fast by ukz on Tuesday July 31, 2018 @01:34AM (#17650772)

Opal: https://github.com/opal/opal

[ Parent | on HN ]