-
-
Notifications
You must be signed in to change notification settings - Fork 723
perf(allocator): reduce operations while Mutex lock is held in AllocatorPool
#11761
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
perf(allocator): reduce operations while Mutex lock is held in AllocatorPool
#11761
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
CodSpeed Instrumentation Performance ReportMerging #11761 will improve performances by 15.05%Comparing Summary
Benchmarks breakdown
|
Mutex lock is heldMutex lock is held in AllocatorPool
101bde6 to
d7a0d0c
Compare
425def8 to
16281db
Compare
d7a0d0c to
bb25d9c
Compare
16281db to
cdc2877
Compare
bb25d9c to
ea5137e
Compare
cdc2877 to
f539f64
Compare
ea5137e to
d8e63cc
Compare
Merge activity
|
…ocatorPool` (#11761) Tiny optimization to `AllocatorPool`. `unwrap_or_else` doesn't require the mutex lock, so drop the lock before calling it.
d8e63cc to
2641030
Compare

Tiny optimization to
AllocatorPool.unwrap_or_elsedoesn't require the mutex lock, so drop the lock before calling it.