3 ms·

I wonder how this compares to v8 over the same code. Will v8 get this smart after running the benchmark? I’d test it myself but I’m on an iPhone right now. I wo

by jitl 3y ago

I wonder how this compares to v8 over the same code. Will v8 get this smart after running the benchmark? I’d test it myself but I’m on an iPhone right now. I wonder if static Hermes will ever end up at break-even or ahead of v8 - especially if doing a lot of FFI in WASM, Hermes might have a better shot at bypassing the memcopy/TextDecoder needed to interop between browser JS strings and WASM utf8 strings in other languages.

deleted 3y ago
[deleted]
iainmerrick 3y ago
If your runtime is a JS interpreter, on iOS you’re almost always better off just using the OS’s interpreter (JSC). Your app will be smaller, and only the OS is allowed to do JIT so it will be much faster. Even without the JIT restriction, you wouldn’t be able to beat JSC as it’s one of the fastest runtimes out there, pretty much level with V8. Static Hermes sounds like a different prospect, though, if it’s able to use TS annotations to compile to mostly-static native code. That could be great for genuinely high-performance TS code. (Although you wouldn’t want to immediately shackle it to React Native...)
- jamil7 3y ago
  I believe JIT is disabled in JSC itself on iOS, to take advantage of JIT in JSC you'd have to go through an out-of-process WKWebView instance.
- saagarjha 3y ago
  JavaScriptCore (the framework) does not use a JIT because it runs in-process. JavaScriptCore (running in a webview) does because it’s out-of-process.
ricardobeat 3y ago
Hermes itself is already faster than JSC, which is on par with V8. This just puts it way ahead and probably closer to Swift/Kotlin code, at least in the realm of mobile apps.
- whizzter 3y ago
  No, the Hermes interpreter is probably on-par with the JSC-Interpreter if this is a comparison made on iOS React Native apps. JSC-JIT is usually on par or ahead of V8, the iOS JIT restrictions really fudges up results since it's so imperative for JS performance. From what I've seen Kotlin(and Swift prob also) semantics are fare more AOT-compile friendly so they're probably a fair bit ahead (depending on how much you gimp your JS target to mimic Asm.JS/Wasm but most regular JS developers won't write code that way).
  - zer0zzz 3y ago
    The Hermes interpreter is probably faster than the others because (afaik) it interprets bytecode produced by the hermes frontend parser (which is don’t ahead of time).
- instagary 3y ago
  What data do you have to back up that statement? We've seen the opposite for networking related activities especially when there are 100's of requests that can happen on certain screens. We've tried using Hermes but didn't see any differences other than the app bundle increasing in size.

by jitl 3y ago

deleted 3y ago

[deleted]

iainmerrick 3y ago

If your runtime is a JS interpreter, on iOS you’re almost always better off just using the OS’s interpreter (JSC). Your app will be smaller, and only the OS is allowed to do JIT so it will be much faster. Even without the JIT restriction, you wouldn’t be able to beat JSC as it’s one of the fastest runtimes out there, pretty much level with V8. Static Hermes sounds like a different prospect, though, if it’s able to use TS annotations to compile to mostly-static native code. That could be great for genuinely high-performance TS code. (Although you wouldn’t want to immediately shackle it to React Native...)

jamil7 3y ago
I believe JIT is disabled in JSC itself on iOS, to take advantage of JIT in JSC you'd have to go through an out-of-process WKWebView instance.
saagarjha 3y ago
JavaScriptCore (the framework) does not use a JIT because it runs in-process. JavaScriptCore (running in a webview) does because it’s out-of-process.

ricardobeat 3y ago

Hermes itself is already faster than JSC, which is on par with V8. This just puts it way ahead and probably closer to Swift/Kotlin code, at least in the realm of mobile apps.

whizzter 3y ago
No, the Hermes interpreter is probably on-par with the JSC-Interpreter if this is a comparison made on iOS React Native apps. JSC-JIT is usually on par or ahead of V8, the iOS JIT restrictions really fudges up results since it's so imperative for JS performance. From what I've seen Kotlin(and Swift prob also) semantics are fare more AOT-compile friendly so they're probably a fair bit ahead (depending on how much you gimp your JS target to mimic Asm.JS/Wasm but most regular JS developers won't write code that way).
- zer0zzz 3y ago
  The Hermes interpreter is probably faster than the others because (afaik) it interprets bytecode produced by the hermes frontend parser (which is don’t ahead of time).
instagary 3y ago
What data do you have to back up that statement? We've seen the opposite for networking related activities especially when there are 100's of requests that can happen on certain screens. We've tried using Hermes but didn't see any differences other than the app bundle increasing in size.