[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:
Related
related to SERVER-16426 d_migrate getActive() mtx is very hot Closed
related to SERVER-15395 Remove "last 100 write lock%" & "writ... Closed
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: SERVER-16342: formatting of top.
Branch: master
https://github.com/mongodb/mongo/commit/d36eac67be457c8a4e11373b0332e2d8d54975e1

Comment by Githook User [ 27/Nov/14 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-16342: remove some snapshot global data that doesn't make sense any more
Branch: master
https://github.com/mongodb/mongo/commit/4e53ba220a73a28a9bd50347c66c347ae97e8b11

Generated at Thu Feb 08 03:40:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.