[SERVER-11951] Report lock yield time (micros) with yield counts Created: 04/Dec/13  Updated: 06/Dec/22  Resolved: 29/Feb/16

Status: Closed
Project: Core Server
Component/s: Concurrency, Diagnostics
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently we report "numYields" or "yields" in various places but we don't report the time spent yielding.

I see this mostly surfacing in lockstats, like those reported via profiling and logging:

// Log entry
20... query test.jstests_orm query: {} ... numYields:1 locks(micros) r:282288 y:101 nreturned:0 reslen:20 141ms



 Comments   
Comment by Scott Hernandez (Inactive) [ 29/Feb/16 ]

Is all time yielding spent waiting for locks?

Comment by Martin Bligh [ 29/Feb/16 ]

Not convinced this makes sense as it's difficult to separate time involuntarily vs co-operatively pre-empted.
Plan is to measure elapsed wall time and time spent waiting for locks.

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