-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
None
-
Affects Version/s: 3.1.3
-
Component/s: Internal Code
-
Windows
-
Platform 6 07/17/15, Platform 7 08/10/15
MongoDB shell version: 3.1.3-pre-
Environment:
• Single mongod with wiredtiger as storage engine
• Windows 2012
• WriedTiger default configuration
• EC2 machine c3.4xlarge
Workload:
• Used YCSB load
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 60% of the CPU
The impact is so big that it mask the different between SSD drive to spin disk on windows.
- depends on
-
SERVER-18922 Choose time source for measuring short durations dynamically at startup
- Closed
- is related to
-
SERVER-17630 Insert only workload under stress - high resolution timer for query operations consume ~17% of execution time
- Closed
-
SERVER-4740 Use monotonic clock sources for Timer
- Closed
- related to
-
SERVER-18613 We can double the WiredTiger YCSB load throughput on windows by eliminate the expensive timer operations
- Closed