Community
Participate
Working Groups
The current implementation of optionality consists in creating all the combinations possible for the IU that has the optional requirements. This works well when there is only a few optional requirements, however it is no so well anymore when one IU has 600 optional requirements, since the number of combinations grows exponentially. Therefore we need to find another way to encode optionality.
Created attachment 94600 [details] stringbuffer patch Here's a patch on the branch that uses StringBuffers in a few places that profiling identified.
new_optionality_branch merged back in HEAD and string buffer changes applied too.
*** Bug 226906 has been marked as a duplicate of this bug. ***