Autosuggest needs work on large datasets

Bug #948284 reported by Mike Rylander on 2012-03-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

From the working branch commit:

Speed up autosuggest in large data environments

The autosuggest infrastructure was assuming the the Postgres query planner
would be able to cope with large datasets without any additional fiddling.
Unfortunately, that proved to be untrue. We also needed a few indexing

 * At the suggestion of Ben Shum, ignore the identifier search class for
 * Added indexes to all joined columns of metabib.browse_entry_def_map.
 * Switched from GIST to GIN indexing of metabib.browse_entry.index_vector
   because GIN, being an inverted index, is /much/ better for prefix matching
   which, in turn, is extremely important for browse and autosuggest.
 * Apply some reasonable sanity-checking limits on suggest queries. This
   means you can't use autosuggest as a reporting tool -- but that's OK
   because it's not one.;a=shortlog;h=refs/heads/user/miker/autosuggest-big_data-speedup

Tested and pushed to master.

Changed in evergreen:
status: New → Fix Committed
Ben Shum (bshum) on 2012-09-20
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers