j-haacker / j-haacker/CryoSwath
Reduce memory footprint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Some functions, especially related to l3/l4 datasets, consume much memory.
**Describe the solution you'd like**
Where possible, limit xarray caching.
**Describe alternatives you've considered**
Alternatively, processes could be forked to ensure data is purged when the forked process terminates.
**Additional context**
I strongly believe it is the xarray caching that floods memory based on `memray` analysis. However, I'm not sure.
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 locating the functions that process l3/l4 datasets and review the reported memray analysis. Determine whether xarray caching causes the memory growth; done means reducing the memory footprint where possible or documenting why the proposed alternatives are needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100