-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.3.0
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
0
A Windows DEBUG concurrency test timed out after 2 hours, fsm_all_replication - mmapv1 (https://logkeeper.mongodb.org/build/567463a09041306f2400f00c/test/567463a0be07c46976010411)
The following tests ran more than 10 minutes:
- remove_and_bulk_insert.js 845092 ms - 14 minutes
- update_and_bulk_insert.js 2758568 ms - 46 minutes
- create_index_background.js 913785 ms - 15 minutes
The same tests on Windows DEBUG concurrency fsm_all_replication - wiredTiger (https://logkeeper.mongodb.org/build/5674638e9041306f2400efef/test/5674638ebe07c469760103f4):
- remove_and_bulk_insert.js 786405 ms - 13 minutes
- update_and_bulk_insert.js 793241 ms - 13 minutes
- create_index_background.js 1061733 ms - 17 minutes
These tests should be sped up, run in a slow suite or possibly be blacklisted for certain platforms.
Perhaps a new slow suite should be considered.
- duplicates
-
SERVER-22100 memory pressure from find/getMore buffer preallocation causes concurrency suite slowness on Windows DEBUG
- Closed