Streamline / clarify / restructure cached getting of responses, parameters, observations from storage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 161
- Forks
- 141
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 138
Description
Now it seems a bit ad-hoc, and is a potential performance hog especially if something is called many times with high frequency. This should be revised. Consider making explicit properties indicating whether the getter is cached or not, and prefer getting the cached.
ref in LocalExperiment:
parameter_info (not cached)
experiment_configuration (cached)
response_info (not cached)
response_configuration (not cached)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting LocalExperiment and tracing the parameter_info, experiment_configuration, response_info, and response_configuration getters to identify which values are cached and which are repeatedly fetched. Compare their call sites and existing tests, if present. Done means the caching behavior is explicit and repeated high-frequency access consistently prefers the cached value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100