Re: i'm going crazy with task

[Adrien Plisson <aplisson-news@stochastique.net>]

Dennis Lee Bieber wrote:
> 	A fancier version would create a task for each entry; the core
> of each task is just:
> 
> delay until start_time
> user_app_main()

this is a bit overkill: if you have many jobs to run, you will start by 
creating that many tasks which will stay idling in the background until 
start_time.

i know that a task does not (or should not) consume processing resources while 
idling, but they still uses memory resources and they certainly uses system 
resources (system objects as handles or such) which may be limited.

a better approach would combine the priority list/queue of the first case with 
the task creation of the second:

while queue.notEmpty loop
     pull job from queue
     delay until start_time
     create a task and pass it the user_app_main function
end loop

and the core of the task will just have to call the given function at startup 
and die when it has terminated. this way the tasks exists only when needed, 
thus limiting resource consumption.

> 	Simulating what /I/ think of when I hear "task scheduler" is
> going to be much more difficult.

it's interresting to see that our interpretation depends on the level we see 
the problem. you see the task scheduler at the very low level of scheduling 
processes for pseudo-concurrent execution on a single processor. i see the task 
scheduler at the high level of deferred process execution.

-- 
rien