Excessive memory use or memory fragmentation when unpickling many small objects
Open
Nobody has claimed this yet.
3.12
performance
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36694 |
|---|---|
| Nosy | @pitrou, @avassalotti, @methane, @serhiy-storchaka, @Paul-E |
| PRs | |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2019-04-21.17:11:20.009>
labels = ['3.8', 'library', 'performance']
title = 'Excessive memory use or memory fragmentation when unpickling many small objects'
updated_at = <Date 2019-05-02.16:43:18.896>
user = 'https://github.com/Paul-E'
bugs.python.org fields:
activity = <Date 2019-05-02.16:43:18.896>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-04-21.17:11:20.009>
creator = 'Ellenbogen'
dependencies = []
files = ['48279', '48280', '48282']
hgrepos = []
issue_num = 36694
keywords = ['patch']
message_count = 8.0
messages = ['340615', '340616', '340617', '341179', '341181', '341193', '341251', '341284']
nosy_count = 5.0
nosy_names = ['pitrou', 'alexandre.vassalotti', 'methane', 'serhiy.storchaka', 'Ellenbogen']
pr_nums = ['13036']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue36694'
versions = ['Python 3.8']
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 reviewing the linked PR #13036 and the attached load.py, common.py, and dump.py files. Reproduce the reported memory behavior for many small objects, then compare the results with the proposed changes. Done means the excessive memory use or fragmentation is addressed and the relevant performance behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100