Improve RelateNG performance for A/L cases in prepared predicates #1201
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improve the
RelateNG
self-noding check to allow A-L cases to take advantage of prepared predicates.Previously, A/L cases were not using the prepared noder cache for predicates which require self-noding (such as
contains
,covers
,relate
etc). This caused significantly poor performance for a common situation. The self-noding check has been refined to allow A/L cases to be use the cached noder.This makes
RelateNG
in prepared mode as fast asPreparedGeometry
for all cases (and it handles more cases).Port of locationtech/jts#1099
For example, a test in
perf_topo_predicate
has dramatically reduced execution time (133x faster):