Disable Solr caches

[WadeBarnes]

As discussed some of the articles listed here caching is only useful when there are repeated queries for the same information, otherwise they can be detrimental to memory use. Queries in OrgBook tend to be random (Humans) or sequential (Spiders and Bots), so there are few, if any, cache hits. This could be, at least part of, the cause for the high memory usage we're seeing in prod.

Try disabling the caches as recommended to see the impact on memory use.

This issue is related to the investigation happening here; bcgov/orgbook-configurations#137

[WadeBarnes]

I created a search-engine image off #759 and smoke tested in dev and test before deploying to prod. Performing some load testing before leaving it over the weekend to collect some metrics.

[WadeBarnes]

Disabling the Solr caches had no effect. If anything the OOM restart issues became worse following the change, though this is just speculation and the increased number of issue could be attributed to query patterns and volume. Some metrics collected here; bcgov/orgbook-configurations#137 (comment).

[WadeBarnes]

This actually helped reduce resource usage. It was actually unbound queries (#762) that were the main issue.