use os.memfd_create in multiprocessing.shared_memory?
Open
Nobody has claimed this yet.
3.13
performance
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37185 |
|---|---|
| Nosy | @pitrou, @tiran, @applio, @pierreglaser, @vinay0410 |
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-06-06.22:20:10.478>
labels = ['3.9', 'performance']
title = 'use os.memfd_create in multiprocessing.shared_memory?'
updated_at = <Date 2019-09-09.15:26:07.601>
user = 'https://github.com/pierreglaser'
bugs.python.org fields:
activity = <Date 2019-09-09.15:26:07.601>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-06-06.22:20:10.478>
creator = 'pierreglaser'
dependencies = []
files = []
hgrepos = []
issue_num = 37185
keywords = []
message_count = 4.0
messages = ['344881', '348974', '351443', '351500']
nosy_count = 5.0
nosy_names = ['pitrou', 'christian.heimes', 'davin', 'pierreglaser', 'vinay0410']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue37185'
versions = ['Python 3.9']
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 reading the multiprocessing.shared_memory implementation and the os.memfd_create documentation, then trace how shared-memory objects are currently created on supported platforms. Compare the platform and resource-management implications; done means the proposed use is implemented with appropriate coverage, or the issue clearly records why it is not suitable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100