That's one more than App Store downloads for iOS users. This past weekend, we reported that Google Play Store now lets Android users install or update up...
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.
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.
I don’t get it either. It seems like getting the first app as fast as possible and proceeding to install it while the next one is being downloaded (like it’s done today) would be the fastest way, but maybe I’m missing something
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.
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.
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.
I don’t get it either. It seems like getting the first app as fast as possible and proceeding to install it while the next one is being downloaded (like it’s done today) would be the fastest way, but maybe I’m missing something
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.