Opened 14 years ago
Closed 13 years ago
#1557 closed defect (done)
Data analysis analyzers do not profit from parallel engine execution
| Reported by: | gkronber | Owned by: | gkronber |
|---|---|---|---|
| Priority: | medium | Milestone: | HeuristicLab 3.3.6 |
| Component: | Problems.DataAnalysis | Version: | 3.3.6 |
| Keywords: | Cc: |
Description
Use parallel constructs explicitly to speed up algorithm execution.
Change History (7)
comment:1 Changed 13 years ago by gkronber
- Milestone changed from HeuristicLab 3.3.x Backlog to HeuristicLab 3.3.6
- Status changed from new to accepted
comment:2 Changed 13 years ago by gkronber
comment:3 Changed 13 years ago by gkronber
- Owner changed from gkronber to mkommend
- Status changed from accepted to reviewing
comment:4 Changed 13 years ago by mkommend
- Owner changed from mkommend to gkronber
- Status changed from reviewing to assigned
The parallel evaluation should be optional and activated depending on the chosen engine. A possible solution would be to introduce an operator parameter that states if the operator should be executed in parallel and which is set by the engine running the algorithm.
comment:5 Changed 13 years ago by gkronber
- Status changed from assigned to reviewing
Together with mkommend it was decided to release this as is in 3.3.6.
comment:6 Changed 13 years ago by gkronber
- Status changed from reviewing to readytorelease
comment:7 Changed 13 years ago by swagner
- Resolution set to done
- Status changed from readytorelease to closed
- Version changed from 3.3.4 to 3.3.6
Note: See
TracTickets for help on using
tickets.
r6728: implemented parallel evaluation in analyzers using ParallelEnumerable extension methods.