4 ms·

they are using Mojo to call native.

• pjmlp 11y ago
  Had to search for what it is. https://github.com/domokit/mojo https://github.com/domokit/mojo I doubt it is faster than Java ART for access to Android Frameworks. Call JNI from C++ it might have delays around 300ms or more per call.
  • badlogic 11y ago
    300ms for a JNI call? In all my years using JNI with Dalvik/ART i have never seen such a degradation. Can you give an example?
    • pjmlp 11y ago
      This is a number I had on my head from the "Using the NDK Performantly (Big Android BBQ 2015)" talk. https://www.youtube.com/watch?v=Wb5HAI73QRE&list=PLWz5rJ2EKKc_HyE1QX9heAgTPdAMqc50z&index=11 https://www.youtube.com/watch?v=Wb5HAI73QRE&list=PLWz5rJ2EKK... From some examples using buffers, maybe I am wrong.
  • mda 11y ago
    I think they update their benchmark results to https://chromeperf.appspot.com/ https://chromeperf.appspot.com/ (browse for benchmarks with mofo prefix) Looks like pretty damn fast to me.
    • pjmlp 11y ago
      This is rendering performance. I mean calling Android APIs via JNI vs calling them from Java.