[SERVER-5980] Track lock queue and active stats per lock (db) Created: 31/May/12 Updated: 06/Dec/22 Resolved: 18/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | metrics, stats | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Track stats on number of waiting requests/acquires per state, per lock, and active threads/ops per state, like we do for the globalLock section.
Also, need stats on the number of acquires/transitions for each locks + state. How many times was the read lock (for each lock instance) acquired and released? |
| Comments |
| Comment by Chelliah Thirunavukkarasu [ 17/Apr/13 ] |
|
The query execution time reported in the log file does not include the time the query spent waiting in queue. Could you please add that stat to the log (profiler etc...) as that time is meaningful for performance analysis. Thanks. |
| Comment by Scott Hernandez (Inactive) [ 02/Apr/13 ] |
|
The things that were done in 2.2 have been removed from the description. |
| Comment by Eliot Horowitz (Inactive) [ 02/Apr/13 ] |
|
much of this was done in 2.2 |