-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a numPathsPerTarget parameter to PathSearch #1596
Conversation
Prior to this change, the PathSearch query used a lot of memory for certain datasets and queries. In that case, the result can not be build and it is not possible to determine where the problem lies. This change adds the parameter numPathsPerTarget. The PathSearch will only search and store paths if the number of paths is lower/equal to the parameter value.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1596 +/- ##
==========================================
+ Coverage 89.08% 89.11% +0.03%
==========================================
Files 371 371
Lines 34437 34456 +19
Branches 3899 3903 +4
==========================================
+ Hits 30678 30706 +28
+ Misses 2484 2480 -4
+ Partials 1275 1270 -5 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor tweaks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick fixes.
Conformance check passed ✅No test result changes. |
Quality Gate passedIssues Measures |
When this parameter is set, the `PathSearch` service limits the number of paths per `[source, target]` pair. This makes it possible to use the path search for cases where enumerating all paths would exhaust the available time and memory constraints.
When this parameter is set, the
PathSearch
service limits the number of paths per[source, target]
pair. This makes it possible to use the path search for cases where enumerating all paths would exhaust the available time and memory constraints.