Slow Aes Decryption In Android
Solution 1:
You should try to bench the time taken without the file writing, i.e. call System.currentTimeMillis()
right before and right after the call to cipher.doFinal()
.
That being said, an Android-based phone typically uses a recent ARM processor clocked at 500 MHz or more, and such a beast is theoretically able to AES-encrypt or AES-decrypt several megabytes worth of data per second.
However, Android code uses an almost-Java virtual machine called Dalvik. Prior to Android-2.2, this is an interpreter (no JIT compiler), which means that it is kinda slow for computing-intensive tasks. If the mediocre performance you observe really comes from the AES operation itself (and not the file writing) then the plausible answer is that your VM provides an AES implementation that is written in Java and interpreted with Dalvik. In that case, there is little cure except hoping for the presence of a better VM implementation (a VM could use a native code implementation for AES; also, with Android 2.2 and later, Dalvik has a JIT compiler which should boost performance of code execution).
Solution 2:
AFAIK, there's no way to get access to the ARM chip's AES encryption/decryption hardware via the Android APIs :-(
This is a huge oversight on Google's part unfortunately...makes using AES on other platforms a LOT faster....
Post a Comment for "Slow Aes Decryption In Android"