LP#1931162: DYM needs some situational optimization user/miker/lp-1931162-DYM-optimization
authorMike Rylander <mrylander@gmail.com>
Mon, 7 Jun 2021 19:57:32 +0000 (15:57 -0400)
committerMike Rylander <mrylander@gmail.com>
Mon, 7 Jun 2021 19:57:32 +0000 (15:57 -0400)
commit0620fa1290f44d0e680c98cfacc381782f7c47ff
treea66360a2d63d867b9ec30f3394228d74789f289c
parent803db1d902823b3fcbbf569094a058076abe58d2
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>
Open-ILS/src/sql/Pg/300.schema.staged_search.sql
Open-ILS/src/sql/Pg/upgrade/XXXX.function.did_you_mean_optimization.sql [new file with mode: 0644]