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:
On Tue, Sep 27, 2011 at 6:01 PM, Brion Vibberbrion@pobox.com wrote:
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
Ok, 'Graz' article in wikipedia-de.zim (same one Christian tested at 20s on an Eclair-based phone, no JIT) I get:
Load time: 5088ms Render time: 131ms
That's on the Nexus One running 2.3.6 (with JIT). About the same load time as I saw with a longer article on a smaller file.
-- brion _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l