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.
Use lru_cache
See original GitHub issueI think lru_cache with suitable default memory limit could be good idea.
Let’s assume, user is working with bare fit/trace objects and does multiple different /same plots, removing them and redoing them again.
Some functions are in really heavy use, e.g. transforming object to Inference object, calculation of summary values.
Also probably some plots could benefit from lru_cache, so “interactive” creation and destroying would be faster.
We would also need a setting to turn it off and change the memory limits.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (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
I have started to work on this. I will soon open a PR to facilitate talking about design decisions for this feature.
I think lru_cache is not something we really need. Usually fjnction is called once per data and mcmc data changes from sample to sample