Related Objects
- Mentioned In
- T111139: Provide documentation for cirrus-suggest API
T105746: Build out an API that exposes ElasticSearch suggester results for a given query
T111078: Run A/B test on the search suggester to measure zero results rate, starting on 2015-09-08
T108767: Make available an XL labs instance with ~350GB available disk space.
T108766: [epic] Setup elasticsearch cluster in labs and build out necessary tooling to use it for hypothesis testing against production data
Event Timeline
I've pulled two sets of logs from fluorine to run through the new suggestions api. Based on this data it looks like we might be able to achieve almost a 40% reduction in the zero result rate of prefix searches by replacing it with the completion suggester.
First set:
This is an unsampled log and contains all prefix searches for enwiki_content that returned no results between 2015-08-26 08:02:23 and 2015-08-26 08:15:49.
API | results | no results | zero % |
prefix_search | 0 | 100000 | 100% |
completion_suggest | 38295 | 61731 | 62% |
Second set
This is every 100th(take 1, throw away 99, repeat) prefix search issued to enwiki_content between 2015-08-25 08:03:30 and 2015-08-26 08:02:23
API | results | no results | zero % |
prefix_search | 288210 | 134469 | 32% |
completion_suggest | 340562 | 82183 | 19% |
Ran same test for dewiki
First set
Unsampled log contains all prefix searches for dewiki_content that returned no results between 2015-08-26 08:02:23 to 2015-08-26 08:48:07
API | results | no results | zero % |
prefix_search | 0 | 100000 | 100% |
completion_suggest | 44678 | 55333 | 55% |
Second set
every 100th(take 1, throw away 99, repeat) prefix search issued to dewiki_content between 2015-08-25 08:03:31 to 2015-08-26 08:02:23
API | results | no results | zero % |
prefix_search | 58641 | 23283 | 33% |
completion_suggest | 69709 | 12216 | 15% |