[SERVER-17630] Insert only workload under stress - high resolution timer for query operations consume ~17% of execution time Created: 17/Mar/15 Updated: 14/Apr/16 Resolved: 18/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Eitan Klein | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | Windows | ||||||||
| Participants: | |||||||||
| Description |
|
Version – Environment: • Single mongod with wiredtiger as storage engine Workload: • Used hammer.mongo to do insert only workload Issue - During insert only workload it's appear that high resolution counter which responsible to notify if operation take longer then X (100msec default) consume ~17% of execution time (see profiler output in the bitmap) When the default of 100 msec logging, it doesn't justify using this expensive call counter, we should consider cheaper alternative such GetTickCount() |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Mar/15 ] |
|
Functionally same as |