Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 4 of Ticket #1355


Ignore:
Timestamp:
01/03/11 01:31:08 (14 years ago)
Author:
swagner
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1355

    • Property Status changed from new to accepted
    • Property Summary changed from Algorithm cleanup itself after it stopped to EngineAlgorithm should cleanup itself after it stopped
    • Property Component changed from ### Undefined ### to Optimization
    • Property Milestone changed from HeuristicLab x.x.x to HeuristicLab 3.3.3

  • Ticket #1355 – Description

    initial v4  
    1 When an algorithm stops, it currently keeps all its state-information (`ExecutionContext` and `ScopeTree`). This is unneccessary because when it is in `ExecutionState` "Stopped", it cannot be resumed (without calling `Prepare`, which causes the deletion of this state-information).
     1When an `EngineAlgorithm` stops, it currently keeps all its state-information (`ExecutionContext` and `ScopeTree`). This is unneccessary because when it is in `ExecutionState` "Stopped", it cannot be resumed (without calling `Prepare`, which causes the deletion of this state-information).
    22
    33Problem: The state-information consumes a large amount of memory when beeing serialized, especially when the population size is large in evolutionary algorithms. This is a significant problem in Hive. When a finished algorithm contains tens or hundrets of megabytes of unnecessary information serialization, deserialization and transmission of jobs is unnecessarily slow.