Set up and connect a cache #377

New issue

Closed

opened 2024-11-20 11:27:53 +00:00 by fricklerhandwerk · 2 comments

fricklerhandwerk commented

2024-11-20 11:27:53 +00:00

(Migrated from github.com)

Update the deployment such that the webserver has access to the cache, and add an integration test to verify that it works.

We have very complex aggregate data that requires long queries, but once compiled the data is largely immutable. In order to leverage that and reduce response times, we need a cache that can be accessed across requests, e.g. Redis. Update the deployment such that the webserver has access to the cache, and add an integration test to verify that it works.

RaitoBezarius commented

2024-11-20 11:37:51 +00:00

(Migrated from github.com)

I am not convinced the case was demonstrated for query set caching, so I strongly do not recommend pursuing this until we have exhausted all the optimization opportunities we have (and we have plenty of them).

👍 1

fricklerhandwerk commented

2024-11-21 08:32:48 +00:00

(Migrated from github.com)

Closing for now as https://github.com/Nix-Security-WG/nix-security-tracker/pull/378 fixes the problem this was supposed to address.