python-trio / python-trio/trio
Document memory consumption of nurseries
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
I'm trying to use trio to write a server. I would like to start one task per incoming connection. However, I am wondering if this might lead to unbounded memory growth in case the nursery keeps track of all started tasks even after they've terminated. It would be great if this could be clarified in the documentation.
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 documentation for Trio nurseries and how they manage completed tasks. Clarify whether a nursery retains terminated tasks and describe the memory implications for one task per incoming connection. Confirm the documentation directly addresses the unbounded-growth concern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100