apple / apple/swift-distributed-tracing
Optimization continuous tracing
Open
- Dominant language
- Swift
- Stars
- 320
- Forks
- 57
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 1
Description
other packages show an impact of about nearly 50%
this package manages an overhead of about 5% (allegedly)
are such optimizations interesting?
https://github.com/fast/fastrace#why-is-fastrace-so-fast
Contributor guide
Research direction
Start by reading the linked fastrace comparison and the issue discussion. Measure or otherwise establish the current continuous-tracing overhead in this package, then clarify which optimization is desired and what overhead target would count as done; the issue currently names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100