Skip to content
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

Investigate whether there's a benefit to caching works/editions in bulk #3

Open
cdrini opened this issue Mar 5, 2019 · 3 comments
Open

Comments

@cdrini
Copy link
Owner

cdrini commented Mar 5, 2019

Although caching internet archive API results in bulk is definitely faster, there might not be a benefit to caching the work/edition objects themselves since they'll only be asked for once.

@tfmorris
Copy link

tfmorris commented Mar 5, 2019

The database also maintains a cache which it can use for repeated requests.

@tfmorris
Copy link

Didn't you already implement this? It looks like IA requests are batched (which is definitely a win since you only pay the R/T latency once rather than N hundred times).

@cdrini
Copy link
Owner Author

cdrini commented Jul 22, 2019

This is caching hits to the postgres copy of the database, not to IA. The question is whether to remove the postgres caching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Solr Builder
  
To Do
Development

No branches or pull requests

2 participants