- 
    Type:Bug 
- 
    Resolution: Incomplete
- 
    Priority:Critical - P2 
- 
    None
- 
    Affects Version/s: 3.0.0-rc11, 3.1.6
- 
    Component/s: Storage, WiredTiger
- 
        Fully Compatible
- 
        Windows
- 
        Platform 4 06/05/15, Platform 5 06/26/16, Platform 6 07/17/15, Platform 7 08/10/15
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
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
•	The machine throughput dropped by 40% after 17 hours of execution 
Will continue and investigate this issue
At this stage
- This is the 2nd repro of the same problem, when I analyzed the dump, I found a huge internal heap fragmentation (see more details on the comment)
- No indication that client stress tool slow down (I observed steady amount of incoming TCP connection per/sec and TCP connection established remained stable)
Next plan – Keep it running to death and debug it when the throughput is significant low.
- is related to
- 
                    SERVER-17421 WiredTiger b-tree uses much more memory than wiredTigerCacheSizeGB -         
- Closed
 
-         
- 
                    SERVER-17424 WiredTiger uses substantially more memory than accounted for by cache -         
- Closed
 
-         
- related to
- 
                    SERVER-18079 Large performance drop with documents > 16k on Windows -         
- Closed
 
-         






