Expose non-synchronized versions of twisted.python.logfile.BaseLogFile and friends
Open
Nobody has claimed this yet.
core
enhancement
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@itamarst reported |
|---|---|
| Trac ID | trac#6971 |
| Type | enhancement |
| Created | 2014-02-13 18:44:06Z |
In high-write situations the synchronization in twisted.python.logfile adds a performance bottleneck, and synchronization isn't always necessary.
Searchable metadata
trac-id__6971 6971
type__enhancement enhancement
reporter__itamar itamar
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__
time__1392317046000000 1392317046000000
changetime__1392317046000000 1392317046000000
version__None None
owner__
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 twisted.python.logfile module, especially BaseLogFile and the related classes named in the issue, and trace where synchronization is applied. Determine the public non-synchronized variants needed and define coverage that distinguishes their behavior. Done means the requested variants are exposed without the synchronization bottleneck and their behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100