memory usage improvements
Open
Feature
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
### Feature Idea
it's leaking memory like crazy. gone up form ~24 GB when stable to full bloated 32+ GB for an identical workflow. it also unloads everything when done, cause it's bloated af. wth is this shit code doing? sell more ram? you gotta be shitting me.
### Existing Solutions
_No response_
### Other
_No response_
Contributor guide
Research direction
No files, tests, entry points, or reproducible workflow are provided. Start by reproducing the reported identical workflow and profiling memory from the stable ~24 GB baseline through 32+ GB usage, including what happens when the workflow finishes. Done means identifying and fixing the leak or unload behavior, then confirming memory returns to the expected level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100