SSLSocket.read does a GIL round-trip for every 16KB TLS record
Open
Nobody has claimed this yet.
3.12
performance
topic-SSL
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 37355 |
|---|---|
| Nosy | @warsaw, @pfmoore, @tiran, @tjguk, @benjaminp, @bitdancer, @njsmith, @dimaqq, @zware, @1st1, @zooba, @Safihre, @pablogsal, @hashbrowncipher, @jakirkham |
| PRs |
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-20.18:42:49.267>
labels = ['expert-SSL', '3.11', 'performance']
title = 'SSLSocket.read does a GIL round-trip for every 16KB TLS record'
updated_at = <Date 2022-03-14.15:49:20.009>
user = 'https://github.com/hashbrowncipher'
bugs.python.org fields:
activity = <Date 2022-03-14.15:49:20.009>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2019-06-20.18:42:49.267>
creator = 'josnyder'
dependencies = []
files = []
hgrepos = []
issue_num = 37355
keywords = ['patch']
message_count = 12.0
messages = ['346156', '379904', '391401', '392584', '392585', '392882', '392883', '396780', '413900', '415035', '415094', '415095']
nosy_count = 16.0
nosy_names = ['barry', 'paul.moore', 'christian.heimes', 'tim.golden', 'benjamin.peterson', 'r.david.murray', 'njs', 'Dima.Tisnek', 'zach.ware', 'yselivanov', 'steve.dower', 'Safihre', 'pablogsal', 'Matthew Rocklin', 'josnyder', 'jakirkham']
pr_nums = ['25478', '31492']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue37355'
versions = ['Python 3.11']
Linked PRs
- gh-102214
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 SSLSocket.read and the linked work in PRs #25478, #31492, and gh-102214. Compare those discussions and implementations with the reported per-record GIL round-trip; done means the issue's performance problem is addressed and the relevant behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, performance, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100