-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
Some core PBT tests recently introduced under SPM-3932 project are very slow to execute compare to the other test core tests that we have. The total amount spent for executing PBT tests in the js core suite account for the 76% of the time required to execute all the tests in this suite. The introduction of these tests caused patches in evergreen to take more time (also the commit queue tasks).
Tests (reference patch)
- jstests/core/query/plan_cache/queries_create_one_cache_entry_pbt.js | 3 m 31s | 27.58 %
- jstests/core/query/partial_index_pbt.js | 2m 56s | 23%
- jstests/core/query/plan_cache/cache_usage_pbt.js | 2m 2s | 15.94%
- jstests/core/query/plan_cache/cache_correctness_pbt.js | 1m 36s | 12.50%
- jstests/core/query/index_correctness_pbt.js | 1m 17s | 10%
- jstests/core/query/run_all_plans_pbt.js | 1m 17s | 10%
- jstests/core/index/express_pbt.js | 35s | 4.57 %
- is related to
-
SERVER-106023 Cache entries that use partial indexes in one branch of an OR can return wrong results
-
- In Progress
-
-
-
- Closed
-
-
SERVER-105836 Only run express_pbt.js and distinct_scan_optimization.js with opt=on
-
- Closed
-