1864936 - Consider using frecency stats to bound autocomplete queries

Status: NEW

(Application Services :: Places, enhancement, P3)

Description

[Mark Hammond [:markh] [:mhammond]]

From github: https://github.com/mozilla/application-services/issues/689.

In #429 I landed support for updating frecency stats (origin_frecency_count, origin_frecency_sum, origin_frecency_sum_of_squares), but don't use them to bound autocomplete queries.

The reason for this is that:

1. They necessarily cause us to have worse search query results (they cause us never to return results with a frecency lower than a cutoff)
2. They're an optimization, and our autocomplete performance seems acceptable currently.

At the moment, I don't think we should use them (hence this bug getting marked as "Backlog" and not "History Polish"), however in the future this could change.

This bug largely exists to document the fact that we don't use them.

┆Issue is synchronized with this Jira Task
┆Epic: Important backlog

Change performed by the Move to Bugzilla add-on.