LP#1931162: DYM needs some situational optimization
authorMike Rylander <mrylander@gmail.com>
Mon, 7 Jun 2021 19:57:32 +0000 (15:57 -0400)
committerChris Sharp <csharp@georgialibraries.org>
Mon, 15 Aug 2022 18:27:18 +0000 (14:27 -0400)
commitaeaa6bad5271d902f0c8c20b752df1c6a4f4ff05
tree59714fb4b49c48fe2be7aad103412dabf2bbd1cd
parent8bddd66088d34aca626efb549fb8759693f23fb4
LP#1931162: DYM needs some situational optimization

For some data sets and some queries the Did You Mean search suggestion
logic can be much too slow. This is mainly in cases where a "misspelled"
word of sufficient length greater than the symspell prefix length is
checked against many short prefixes that have many long suggestions
attached to them.

This commit optimizes for that case in particular by testing the length
of suggestions and prefix keys against the user input to avoid
unnecessary tests.  Futher, it captures the edit distance of suggestions
that pass that test in-line, avoiding expensive retesting, and caches
the short-cutoff edit distance when in low-verbosity mode to avoid
future different-but-not-too-different suggestions coming from the same
prefix key.

It additionally provides a general optimization by batching the capture
of suggest counts to avoid per-suggestion secondary lookups, and a
micro-optimization of ordering suggestions by length at distance cache
time.

Signed-off-by: Mike Rylander <mrylander@gmail.com>
Signed-off-by: Shula Link <slink@gchrl.org>
Open-ILS/src/sql/Pg/upgrade/XXXX.function.did_you_mean_optimization.sql [new file with mode: 0644]