Current load time for the search page without any filters is about 3.76 seconds with the response from Elasticsearch being 6.54 MB after the optimizations made to the Search API indexing process.
[x] Limit the properties returned by Elasticsearch to what can be filtered or displayed in the table
[ ] See if we can remove nested and/or parent-child relation related searches
[ ] We rely on term specific aggregations which can be memory heavy, can we tweak our existing model to remedy this? (e.g. for the property has_rui_information we do a term aggregation for either "True" or "False". How much faster would it be if we stored it has 0 or 1 instead?)
[x] Remove created_timestamp and last_modified_timestampaggregations
Current load time for the search page without any filters is about 3.76 seconds with the response from Elasticsearch being 6.54 MB after the optimizations made to the Search API indexing process.
Some things to look into (related to https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-search-speed.html)
has_rui_informationwe do a term aggregation for either "True" or "False". How much faster would it be if we stored it has 0 or 1 instead?)created_timestampandlast_modified_timestampaggregations