[jboss-jira] [JBoss JIRA] (JBRULES-3535) Planner: DistinctMoveSelector

[Geoffrey De Smet (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet updated JBRULES-3535:
--------------------------------------

    Description: 
A shuffled move selector needs to cache, causing memory problems.
A just-in-time random move selector might produce duplicates.

Solution: put a DistinctMoveSelector in front of the just-in-time random move selector so it filters out moves that have already been iterated.
- use Weak or Soft references to avoid OutOfMemory errors?
- make sure it's cleared properly during round-robin selection over multiple steps.

  was:
A shuffled move selector needs to cache, causing memory problems.
A just-in-time random move selector might produce duplicates.

Solution: put a DistinctMoveSelector in front of the just-in-time random move selector so it filters out moves that have already been iterated.
Note: make sure it's cleared properly during round-robin selection over multiple steps.


    
> Planner: DistinctMoveSelector
> -----------------------------
>
>                 Key: JBRULES-3535
>                 URL: https://issues.jboss.org/browse/JBRULES-3535
>             Project: Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-planner
>            Reporter: Geoffrey De Smet
>            Assignee: Geoffrey De Smet
>            Priority: Minor
>
> A shuffled move selector needs to cache, causing memory problems.
> A just-in-time random move selector might produce duplicates.
> Solution: put a DistinctMoveSelector in front of the just-in-time random move selector so it filters out moves that have already been iterated.
> - use Weak or Soft references to avoid OutOfMemory errors?
> - make sure it's cleared properly during round-robin selection over multiple steps.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira