Hector Martin (@marcan@treehouse.systems)
social.treehouse.systems
Attached: 1 image Wait, 20 *milliseconds*? Either their kernel scheduler config is completely out of whack, or ARM/Qualcomm really screwed this one up. Apple cores can boost to max in around 50 *micro* seconds. 20 milliseconds is just broken. That's more than one frame, and that's how you get janky UI response and dropped frames. I hope this was a config issue and these cores/designs really don't take 20ms to increase clocks (I could see that with a really bad regulator/power delivery system...) From: https://chipsandcheese.com/2023/08/11/arms-cortex-a710-winning-by-default/
  • Sheltac@lemmy.world
    39·
    1 year ago

    Interesting, I always thought it had to do with Android’s ungodly software stack which at some point involves, of all things, fucking java.

    • fartsparkles@sh.itjust.worksEnglish
      9·
      1 year ago

      Android doesn’t use Java at a byte-code level and never has, as far as I can tell. Source code was written in Java since mobile developers were so used to it but Android never ran the JVM, they do their own thing with Java source.

      You can dislike Java syntax but the software stack on Android wasn’t Java’s.

      • Sheltac@lemmy.world
        20·
        1 year ago

        Wait, thats is very different from what I read back in the day. I know there was a point at, I dunno, android 5 where they started doing something different with java, but my impression was that android always ran a JVM of sorts. And frankly, given how it performs even on the highest-end devices, that was really easy to believe.

        I guess I need to do some research now.

        • bluefirex@lemmy.world
          36·
          1 year ago

          No you’re correct. Android does run a JVM, just not Oracle’s. That has always been the case. Back in the day it was Dalvik, nowadays it’s ART.

        • fartsparkles@sh.itjust.worksEnglish
          9·
          1 year ago

          Pretty sure it was Dalvik virtual machine that Java was compiled to byte code for before 4.4 when they deprecated Dalvik for Android Runtime (ART), fully dropping Dalvik in 5.

          • saua@troet.cafe
            7·
            1 year ago

            @fartsparkles @Sheltac Android always ran dalvik bytecode and never Java bytecode
            The change to Art was just a replacement of the “VM”, but didn’t change what byte code was run. It’s similar to how Hotspot improved the Java VM while also not fundamentally changing that it’s running Java bytecode.

      • vzq
        11·
        3 months ago

        deleted by creator

      • K0bin@feddit.de
        2·
        1 year ago

        They compile Java Bytecode to Dalvik Bytecode and run that on the Android Runtime which is a tiered JIT compiler.

        It still inherits the issues of Java such as the GC, no stack allocated value types, poor cache locality, etc. Although tbf the GC on Android is pretty fucking good these days and doesn’t pause the world anymore.

  • Immersive_Matthew@sh.itjust.worksEnglish
    12·
    1 year ago

    I have no experience with iOS but I do develop for the Meta Quest which runs on Android and wow is it jank. One solution for apps up to 2GB and another for up to 4GB and yet another, much more complicated solution for apps over 4GB. Is iOS like this too?