SirMungus wrote
So, there would undoubtedly be a performance impact, even not taking into
account the "new HashSet()" in the getResults() call. Whether it would be
significant enough in real world scenarios to warrant a much more complex
implementation requires more knowledge of Drools's user base than I
possess, for sure. My guess is that Wolfgang's second scenario above is
generally unrealistic. But, if it is routine for rules with collectSet()
to end up with sets involving thousands of objects like the /second/
scenario, that could certainly be an issue.
Goodness. I meant to say that the first scenario (instead of "second"
italicized above) could potentially be realistic. The larger the sets,
larger the penalty each time getResults() is called.
--
View this message in context:
http://drools.46999.n3.nabble.com/BUG-5-3-0-Final-CollectSetAccumulateFun...
Sent from the Drools: Developer (committer) mailing list mailing list archive at
Nabble.com.