-
Notifications
You must be signed in to change notification settings - Fork 42
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
Potential optimisations for requests that do not ask for a filter #2093
Comments
thanks @ml-evs, with basic indexes in mongodb, the default load can be made fairly fast except for the total number of structures ( |
Maybe this is a good idea after all, if a web client always hits the same request, we could cache these as JSON files that are served statically rather than via the API, e.g., via the config file:
|
e.g., on server startup, take a series of chunked blobs corresponding to the default sort order of the API, then if a user requests with no filter and no page limit, return this static chunked data directly.
cc @JonathanSchmidt1 @eimrek (maybe this is a useful optimisation for e.g., the Li-ion set too)
The text was updated successfully, but these errors were encountered: