I noticed that you use action=query with both generator=prefixsearch and list=prefixsearch.
IIRC when we looked at this (it was when we looked at the way some API consumers generates their requests) we noticed that it generates 2 prefixsearch queries on the backend. I think this adds unnecessary latency.
@dcausse -- discovery mailing list
This is correct. The additional parameters from the API call are unnecessary and can be safely removed with no adverse effects.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Removing the 'list' param from the type-ahead API call | wikimedia/portals | master | +5 -7 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | debt | T130755 [EPIC] Portal Production release: bug fixes and small updates | |||
| Resolved | Jdrewniak | T129639 Search Suggestions API call doesn't need the list=prefixsearch parameter |
Change 276783 had a related patch set uploaded (by Jdrewniak):
Removing the 'list' param from the type-ahead API call
Change 276783 merged by jenkins-bot:
Removing the 'list' param from the type-ahead API call
Resolving this ticket - will go into production with this: https://phabricator.wikimedia.org/T130755