-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.8.0-rc4
-
Component/s: Performance, Storage
-
None
-
Environment:Mongodb using the TCMalloc memory allocator.
-
Fully Compatible
-
ALL
Performance degradation due to TCMalloc scalability with very large number of threads. After a few minutes of running with hundreds of threads, the large majority of CPU time is spent scavenging memory. As this often occurs in critical sections, system throughput may degrade by an order of magnitude or more. Increasing the TCMalloc thread cache to its maximum of 1 GB does not avoid this problem. Using the system allocator does, but costs performance in most other cases.
- is duplicated by
-
SERVER-16879 Degraded performance on rc5 (mms-prod-pings1)
- Closed
- is related to
-
SERVER-22763 Investigate performance of new gperftools upstream MarkThreadTemporarilyIdle
- Closed
-
SERVER-31839 Investigate JEMalloc Performance Versus TCMalloc
- Closed
- related to
-
SERVER-16131 Log File Blowing up on sharded ycsb run in EC2 (or inserts too slow)
- Closed
-
SERVER-20104 WT high memory usage due to high amount of free memory accumulated by TCMalloc
- Closed
-
SERVER-16879 Degraded performance on rc5 (mms-prod-pings1)
- Closed