On Tue, Sep 27, 2011 at 1:51 PM, Christian Pühringer <cip(a)gmx.at> wrote: Just to warn: run 'git submodule init && git submodule update' after cloning the repository, or Eclipse will whinge about being unable to find the xz-java sources. :) I did a quick test on my Nexus One (running Android 2.3.6, so with JIT). There are some faster processors out there on higher-end phones, but there's also a lot of cheaper phones that aren't going to be any faster than this. The wikipedia-de.zim test file hasn't downloaded here yet so I started with a smaller file generated from: http://en.wikipedia.org/wiki/User:Brion_VIBBER/Books/SmallZimTest Fastest of three runs each: 'Barack Obama' (a fairly long article with a few hundred KB of HTML) Load time 5298ms Render time 439ms 'Husiatyn Raion' (a shorter article) Load time 1789ms Render time 23ms Better than 20 seconds, but still pretty slow; I'm not sure offhand how the articles get placed in their blocks so there may well be worse worst cases. :( Definitely worth trying the native-code library at least for the LZMA -- though in a worst case, a few seconds to load isn't worse than you'll have on a slow mobile data network. :) Make sure it runs on a background thread and shows a spinner or progress bar if we do end up having to run fetches this slowly on some platforms... -- brion

Hi Brion, Thanks for trying this out. Performance gain is basically as expected, but looks like that we should switch to native xz support. Alternatively we could reduce the cluster size, although this would impact compression ratio. Anybody has an idea whether cluster size reduction is feasible? (Reduction would need to be about 1:10, so pretty significant). Regarding image support after some more trials I believe that the replace-imgsrc-withbase64data in javascript may work sufficiently well for first zim support. It may be pretty slow if a lot of images need to be loaded, but on mobile phones anyway typically zimfiles with no or few images are the main use case (because with all images the zim files are extremely large). In the future (=when ice cream sandwich devices available) it makes sense to switch to/add support of the WebViewClient.shouldInterceptRequest-approach, as this is supposed to be much faster. We should talk to the phonegap team, whether they could add support for this, so that plugins can use it. Best regards, Christian Am 28.09.2011 21:24, schrieb Brion Vibber: