Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
limit cache size?
See original GitHub issueI ran into an issue when running lots of astroquery queries where my cache ballooned in size to ~10s of Gb—and I didn’t realize there was a cache until it was enormous, so this has caused some minor headaches with my home directory quota, etc. I raised the issue over at astroquery that there should be a (perhaps user-configurable) limit on the cache size, so that old stuff gets overwritten if need be? @keflavich suggested I make this same suggestion over here.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Caching is not for the faint-hearted, but yes, you can give it a try.
Let me add that the cache preserves modification and access times, if the underlying filesystem tracks those, so in about five lines of code you could delete from the cache anything that hasn’t been accessed in six months. (Or six months if big and a year if small, or…)