Last modified: 2014-03-17 13:24:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64726, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62726 - CirrusSearch: If the search didn't find many results then rerun the suggester with more time consuming settings
CirrusSearch: If the search didn't find many results then rerun the suggester...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CirrusSearch (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-17 13:24 UTC by Nik Everett
Modified: 2014-03-17 13:24 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nik Everett 2014-03-17 13:24:47 UTC
After https://gerrit.wikimedia.org/r/#/c/119041/ we will be running the suggester with faster, less accurate settings.  They'll be good enough to find lots of suggestions, but not all.

Proposal: if the search didn't find many results then rerun the suggester with more aggressive settings.  Stuff like:
prefix_length: 1,
max_errors: 3,
confidence: 1.1,

Also, we might want to only do this if the suggest run with the query didn't find anything.  Not sure.  We could also check the score on the result and use some cutoff.  Dunno.


Note: prefix_length and max_errors can cause much more CPU usage.  I'm suggesting just a single notch more on each setting but that still would be quite a bit.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links