[SERVER-60906] Reduce runtime of fuzzer for pipelines that contain $densify Created: 21/Oct/21 Updated: 29/Oct/23 Resolved: 25/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QO 2021-11-01 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 48 | ||||||||
| Description |
|
The details are in BF-23054, but in a nutshell there is a high probability that pipelines with $densify will end up generating 500k documents resulting in very slow runtimes and/or result comparison times. The reason this happens frequently is because we are using a fairly wide date range, which combined with a very small time unit (e.g. milliseconds) means there are many documents needed to fill the entire range of values. |
| Comments |
| Comment by Githook User [ 22/Oct/21 ] |
|
Author: {'name': 'Nicholas Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}Message: |