We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
a nice feature to have would be to allow retention of cached data so that data does not need to be redownloaded.
The text was updated successfully, but these errors were encountered:
Based on the size of the data I would image a disk cache, right?
Sorry, something went wrong.
Yes, I was imagining:
To save:
{param_hash}_{record_count}.p
to fetch before performing query:
I'm not certain if record_count is the only parameter to look at, however. Records could be updated without changing the count of records.
I usually go to https://joblib.readthedocs.io/en/latest/auto_examples/memory_basic_usage.html for that kind of operation. If you choose to not save on disk we can use functools.lru_cache from the standard library.
functools.lru_cache
No branches or pull requests
a nice feature to have would be to allow retention of cached data so that data does not need to be redownloaded.
The text was updated successfully, but these errors were encountered: