[SERVER-16342] Top stats lock is hot Created: 27/Nov/14 Updated: 05/Apr/17 Resolved: 06/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Storage 2016-12-12 | ||||||||||||
| Participants: | |||||||||||||
| Comments |
| Comment by Daniel Gottlieb (Inactive) [ 06/Dec/16 ] |
|
Running the benchmarks and looking at likely workloads to replicate this observation have shown a ~2.0% improvement with a patch that does not record any `top` statistics (including not grabbing the lock at all). A patch that acquires the lock, but does not record any statistics is a ~1.7% speedup. The lock is not currently a major contributor to performance. |
| Comment by Eric Milkie [ 16/Nov/16 ] |
|
We should reconfirm this is still an issue. |
| Comment by Githook User [ 27/Nov/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Githook User [ 27/Nov/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |