You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently prioritize title search over full-text search results, because title search tends to be more accurate, and if we get enough title-search results, we might never actually load the ft ones. If the user scrolls to the end of the search list, we could load some more ft results (or do it if the user scrolls past the first half of results showing).
The downside is that calls to the libzim worker are currently somewhat "expensive" and noticeably slow even on powerful desktop machines. Is the extra CPU usage worth it when 99% of the time we get fast and accurate results within the first user-selectable window of results?
The text was updated successfully, but these errors were encountered:
@Rbcoder1 You should work on one issue at a time. If you prefer this one, which might be easier than the change of the whole UI, I can assign this to you and unassign you from #523. Just let me know which you prefer to work on.
We currently prioritize title search over full-text search results, because title search tends to be more accurate, and if we get enough title-search results, we might never actually load the ft ones. If the user scrolls to the end of the search list, we could load some more ft results (or do it if the user scrolls past the first half of results showing).
The downside is that calls to the libzim worker are currently somewhat "expensive" and noticeably slow even on powerful desktop machines. Is the extra CPU usage worth it when 99% of the time we get fast and accurate results within the first user-selectable window of results?
The text was updated successfully, but these errors were encountered: