Feature #6614
closedIntellectual scheduling
0%
Description
Sometimes scheduling can be done more intellectually, e.g. we can try to solve more tasks with initially lower memory limits and re-solve them one or more times (there can be an option) if they meet memory limit. Since it depends on specifics of verification tasks to be solved (e.g. testing verification tasks require very few resources while complicated rule specifications likely require the most of them) it is better to implement this scheduling within VTG.
Updated by Evgeny Novikov over 7 years ago
- Description updated (diff)
- Category changed from Scheduling to Tasks generation
- Priority changed from Normal to Urgent
Updated by Evgeny Novikov over 7 years ago
- Assignee deleted (
Ilja Zakharov) - Priority changed from Urgent to High
There are too many very high priority issues. This one can be done after really important features will be supported.
Updated by Ilja Zakharov about 7 years ago
- Priority changed from High to Urgent
- Target version set to 2.0
Rising the priority since it is related to #7470 and blocks it.
Updated by Evgeny Novikov almost 7 years ago
- Assignee set to Ilja Zakharov
I am not sure that this feature should be fully implemented together with #7470, although they definitely should be based on the same ground.
Updated by Evgeny Novikov almost 7 years ago
- Subject changed from Speculative scheduling to Intellectual scheduling
- Description updated (diff)
Updated by Evgeny Novikov over 6 years ago
- Target version changed from 2.0 to 1.1
This issue is not strictly bound with purposes of 2.0 that targets verification of C software.
Updated by Ilja Zakharov over 6 years ago
Implemented in 6614-speculative-scheduling.
Updated by Evgeny Novikov over 6 years ago
- Related to Feature #9167: Track speculative wall and CPU time added
Updated by Evgeny Novikov over 6 years ago
- Status changed from Resolved to Closed
Tests passed demonstrating a very-very small change in total wall time. So, I merged the branch to master in aa70aed85.
Let's wait for very rapid verification tasks generation or/and quite complicated verification tasks when speculative scheduling will allow to win much time!