Closed Tonku closed 10 years ago
I ran a loop test and found out that the decoding is that one that's heavy. I have a dev branch where I run the encoding and decoding on a background thread. Decoding is still heavy, but allocation seems to be better. You can give it a try here https://github.com/seanooi/iOS-WebP/tree/dev and do let me know how it goes.
Hi I found the lib is bit slow and utilise more cpu when encode to WebP Am i right..?