[jboss-jira] [JBoss JIRA] (JBRULES-681) Multi-threaded Solver: construction heuristics, local search, ...

Geoffrey De Smet (JIRA) jira-events at lists.jboss.org
Tue Mar 13 08:57:48 EDT 2012


    [ https://issues.jboss.org/browse/JBRULES-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676386#comment-12676386 ] 

Geoffrey De Smet commented on JBRULES-681:
------------------------------------------

The design not to break delta based incremental score calculation:

- Every planning entity gets an internal ID as soon as Planner knows about it. Each thread has one solution cloned. The entities and their id are stored in a map per thread.
- When a Move is migrated from the step thread to the move thread, each of it's planning entities (which includes any toPlanningValue that is a planning entity) is replaced by the move thread's correct planning entity.
                
> Multi-threaded Solver: construction heuristics, local search, ... 
> ------------------------------------------------------------------
>
>                 Key: JBRULES-681
>                 URL: https://issues.jboss.org/browse/JBRULES-681
>             Project: Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-planner
>            Reporter: Geoffrey De Smet
>            Assignee: Geoffrey De Smet
>            Priority: Critical
>
> Use Future's to spread all possible moves in each step over a number of threads.
> This number of threads is equal to the number of cpu's by default, as no IO is done during solving.
> Problems:
> - each thread will needs it own WorkingMemory and during a step, each working memory will need to be updated
> - a bunch of classes will need to be thread safe, or at least visibility save, such as bestsolutionrecaller.
> - Barriers will be needed to collect the result of each step
> - decks might be a great way to spread out the load

--
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

        


More information about the jboss-jira mailing list