-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement a request cache #137
Comments
Do we still plan on doing this? It seems, that SILO can handle large number of requests. Or do we keep this open, until we see the results from the production server? |
Yes, let's keep it for a while and then analyze the response times. |
As discussed, we will now introduce a request cache, similar to v1. This is necessary, due to large load on SILO (mainly on the collections page.) See GenSpectrum/LAPIS-SILO#298 |
I updated the description. |
Also make sure to invalidate the cache when SILO has a new data version
Also make sure to invalidate the cache when SILO has a new data version
Also make sure to invalidate the cache when SILO has a new data version
Also make sure to invalidate the cache when SILO has a new data version
Cache requests to reduce load on SILO.
Details:
The text was updated successfully, but these errors were encountered: