Changes between Initial Version and Version 1 of Ticket #305
- Timestamp:
- Jul 2, 2007, 5:49:37 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #305
- Property Keywords keep-in-memory waiting-for-memory removed
-
Ticket #305 – Description
initial v1 9 9 Could I therefore make a few suggestions: 10 10 11 * When Boinc reaches a 'waiting for memory' state on one task, it shouldn't start another high-memory task.11 * When Boinc reaches a 'waiting for memory' state on one task, it shouldn't start another high-memory task. 12 12 13 * If one of the tasks has been recently checkpointed, and boinc is in a 'waiting for memory' state, it should remove it from memory even if the 'keep in memory' flag has been set to Yes.13 * If one of the tasks has been recently checkpointed, and boinc is in a 'waiting for memory' state, it should remove it from memory even if the 'keep in memory' flag has been set to Yes. 14 14 15 * The scheduler should be reluctant to load new tasks into memory if there is a task already in memory which can be run instead. Perhaps if STD is less than the timestep interval for a project, and it already has a task running, the scheduler should continue running an in-memory task from another project instead.15 * The scheduler should be reluctant to load new tasks into memory if there is a task already in memory which can be run instead. Perhaps if STD is less than the timestep interval for a project, and it already has a task running, the scheduler should continue running an in-memory task from another project instead. 16 16 17 17 The memory deadlock issue was with version 5.8.16 of the Boinc manager, and the two-tasks-for-each-project issue was with version 5.10.6. If these have already been resolved in the current head version then please feel free to close this Trac item.
