Comment 4 for bug 1242467

I've implemented some very basic docset support on my local machine.

The main problem I've encountered is a significant startup slowdown when there are huge docsets in the books directory. For example, the Java_SE7 docset has about 50,000 tokens which are loaded into memory by the DevHelp on startup. The startup time with Java docset enabled is about 15 seconds on my laptop with a Core i7 CPU and an SSD disk. The search is still quite fast. As I can see, it's not so easy to avoid this problem at the moment. Zeal, for example, uses the sqlite database directly to not load all the symbols into memory.

I still can improve my first draft a little bit and prepare a pull request in a few days. But a more efficient approach is obviously required.