[I] vol2: ScopeEvaluator.invokeFilter resolves Method via reflection on every scope check call [incubator-kie-drools]

["mdproctor (via GitHub)" <gi...@apache.org>]

mdproctor opened a new issue, #6722:
URL: https://github.com/apache/incubator-kie-drools/issues/6722

   ## Found during code review of #6718
   
   `ScopeEvaluator.invokeFilter()` runs `Arrays.stream(pred.getClass().getMethods()).filter(...)` on every invocation. This is called per scope check (not()/exists() evaluation) on the hot path.
   
   `ReteEngine` already resolves the `Method` once at wiring time (`resolveTestMethod`). `ScopeEvaluator` should do the same — cache the resolved `Method` on the `LambdaConstraint` at store time, or pass a pre-resolved `Method` alongside the predicate.
   
   Refs #6718, #6714 (TupleFilterProcessor)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org