-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Not Applicable
-
None
After the change of WT-4571, there was weird performance degradation in update-only-btree wtperf found when using high number of threads (on high performance instances like i3.metal).
When we enabled diagnostic to build, we usually expected to have better performance, but in this case, the opposite situation occurs. On i3.metal instance, more than 10% performance degraded in 32 threads and 128 threads. (weird that it is improved in 64 threads)
Threads | 1 | 8 | 16 | 32 | 64 | 128 |
w/ diagnostic | 93,732 | 456,995 | 848,094 | 920,666 | 874,134 | 920,903 |
w/o diagnostic | 177,560 | 458,560 | 756,902 | 804,446 | 897,492 | 802,055 |
More related results can be found on this Jira comments: https://jira.mongodb.org/browse/WT-4571?focusedCommentId=2170548&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2170548
- is related to
-
WT-9074 Reconsider spinlocks in transaction ID allocation path
- Open