Fuzzy search consumes over 65% of CPU

[stefanos82]

I have tried both searches, with and without fuzzy search; with fuzzy search it consumes over 65% and delays to print out the results, whereas without it, it consumes up to 12% at most and outputs the results immediately.

[trollixx]

Interesting. How many docsets do you have installed? I just tested it on my weak laptop and couldn't get the CPU utilization go over 18%.

[stefanos82]

Currently I have 29, but in the past I have had even more 😄

[stefanos82]

Look at this...

Zeal is just open in idle mode:

Don't you think so much memory is over-consumed?

[trollixx]

I bet half of that is Qt WebEngine. 😂

Then we keep indices in memory, that doesn't help. I've been thinking about maintaining a cross-docset index, but it's a bit of extra work.

[stefanos82]

When you say you keep indices in memory, which "memory" exactly, app's memory or database's?

[stefanos82]

I think I have a hypothesis what might cause the sudden CPU spike...

With fuzzy search enabled, it seems like when you search globally, not based on a docset inner search, it finds the data you are looking for and tries to start the web server to load the content which it causes a sudden CPU jump out of the blue until it completes the inner page rendering; it takes a few milliseconds, but the behavior is very obvious to say the least.

Now here's the interesting part: when you disable fuzzy search and you repeat the same process as before, the results are instant without CPU spike at all; in reality, the CPU remains the same, no more than ~5% at most!

[trollixx]

Please try 6d4b65c. That should make the search a bit less demanding.