Community
Participate
Working Groups
We have been investigating problems where either an optimal solution was not found or was not found within specified conflict limits. It is difficult to reproduce these problems on separate machines because the input order depends on which VM the person is running, etc. We should consider sorting the input to SAT4J to get consistent solutions across VMs.
The code to sort the IU is already inside the projector code, but only activated in debug mode. In p2cudf, I activated that code to have reproducible results and did not noticed a decrease of performance, even if we are treating more than 50K IUs. I suggest that we always sort the IUs to facilitate future debugging and maintenance of p2. Waiting for a go before doing a commit.
I now this inconsistency has caused problems a few times in the past so being more consistent here would help. I noticed when this was last visited in bug 267504 there was some performance concerns with it, but it sounds like you no longer see this hit.
I committed the code on HEAD.