-
Notifications
You must be signed in to change notification settings - Fork 492
refactor(stacktrace): remove unnecessary locking from segmentPrefixTrie #4154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(stacktrace): remove unnecessary locking from segmentPrefixTrie #4154
Conversation
BenchmarksBenchmark execution time: 2025-11-25 13:22:32 Comparing candidate commit 4ee937d in PR branch Found 5 performance improvements and 0 performance regressions! Performance is the same for 10 metrics, 0 unstable metrics. scenario:BenchmarkCaptureStackTrace/10-25
scenario:BenchmarkCaptureStackTrace/100-25
scenario:BenchmarkCaptureStackTrace/20-25
scenario:BenchmarkCaptureStackTrace/200-25
scenario:BenchmarkCaptureStackTrace/50-25
|
eliottness
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working implem. Feel free to ignore comments if you don't feel like it
Which comments? 😅 |
89e0450 to
0cbb439
Compare
The segmentPrefixTrie follows a write-once-read-many pattern where all
writes occur during package initialization before any concurrent access.
After initialization, the trie is effectively immutable and can be safely
read by multiple goroutines without synchronization overhead.
Signed-off-by: Kemal Akkoyun <[email protected]>
bf07665 to
738be05
Compare
darccio
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Merge main to fix the broken system-tests, as it seems that GHA cache was flaky.
…ol_with_zero_allocation_implementation
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
[email protected] unqueued this merge request |
…ol_with_zero_allocation_implementation
|
/remove |
|
View all feedbacks in Devflow UI.
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
replaces #4149
What does this PR do?
The segmentPrefixTrie follows a write-once-read-many pattern where all
writes occur during package initialization before any concurrent access.
After initialization, the trie is effectively immutable and can be safely
read by multiple goroutines without synchronization overhead.
Something I have overlooked when I working on this initially.
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!