Memory record of tasks is measured from inside the task
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Right now the memory recorded if you use TASK_DIAGNOSTICS = True you'll receive a record reported by a background thread in the process performing the task (the forked child process). This will increase the amount of memory usage by some amount from the thread recording it. It would be better to have the parent process record the memory usage so that it wouldn't influence the process being measured.
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 TASK_DIAGNOSTICS and the code that records task memory, then trace how the forked child and parent process communicate during task execution. Done means the parent records the child task's memory without the recording thread increasing the measured usage; add or update tests around this behavior if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100