• JackGreenEarth@lemm.ee
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    3
    ·
    1 month ago

    What’s the point? Updating four apps four times as slowly simultaneously is the same as updating four apps at four times the speed consecutively, and you would have the same internet speed either way.

    • unknowing8343@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      19
      arrow-down
      1
      ·
      1 month ago

      In my experience (not in Android apps but in Arch Linux updates) parallel downloads are almost always waaay faster. Magnitudes faster. Using multiple cores? Is it the bottleneck actually enforced by the server? I don’t know, I just know it works.

      And if they did it, it’s because it works on Android too.

      • wander1236@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 month ago

        That’s not how it was done before, though. It wouldn’t download update A, start installing A, then trigger downloading update B while A was installing. A would have to finish installing before B could even start downloading.

        Especially for smaller updates, the overhead of the network handshaking to start the download can actually make doing 3/4 downloads at once faster than sequencing them. For larger updates, it matters less, but it’s not a negative.

        You can still use an app while the update is downloading. You only can’t while the update is installing, and installations still have to happen sequentially (limitation of Android). It only really matters if you want to specifically use an update right away, but then you can just manually trigger the update for just that app.