The task list can become a very huge object, and keeping it in RAM would have a
severe impact on performance.
Since we already store it on disk, we could go one step further and do
scheduling from disk. For simple strategies (FIFO, LIFO, random) the extraction
of a new task is straight forward and won't require the storage of metadata.
For "smarter" strategies, some sort of information on the stored tasks should
be kept in RAM.
Original issue reported on code.google.com by nofatclips on 4 Dec 2011 at 10:06
Original issue reported on code.google.com by
nofatclips
on 4 Dec 2011 at 10:06