Version –
Mongod RC11binaries

Environment:

• Single mongod with wiredtiger as storage engine
• Windows 2012
• WriedTiger configured with 1GB cache
• EC2 machine c3.large

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()