This mechanism is described at the Android developers site as follows:
zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
In short: .apk
content can be easier/faster/more optimal accessed due to the order of data inside the packed file.
For deeper information, there's a "complete guide" available at AddictiveTips: What Is Zipalign In Android And How To Make Apps Zipaligned, which answers the second part of your question:
Quite understandably, situation would be reserved for unaligned application packages. Resource reading would be slow and memory usage would be on the higher end of the spectrum. It would also depend on how many unaligned applications are present. For example, if less number of applications with an unaligned home application, you?d see slower application launch times. This is the best case scenario. For a worst case scenario, having a number of unaligned applications will result in the system repeatedly starting and killing processes, struggling with lags and huge battery drain.
playoff schedule charles addams pinewood derby cars republican debate tonight tinker tailor soldier spy rich forever rick ross project runway all stars
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.