From: Jacob Sparre Andersen <sparre@nbi.dk>
Subject: Re: Task with access to itself?
Date: Wed, 12 Dec 2012 21:25:07 +0100
Date: 2012-12-12T21:25:07+01:00 [thread overview]
Message-ID: <87k3snj9wc.fsf@adaheads.sparre-andersen.dk> (raw)
In-Reply-To: ka85lk$8pe$1@dont-email.me
Jeffrey Carter wrote:
> Jacob Sparre Andersen wrote:
>> 2) Control over which order the worker tasks are activated in.
>
> Why? They're all identical. In our case, we only allocate a task when
> there's a job to do and no existing task to handle it; such tasks are
> of course activated in the order they're created.
Because I prefer to activate the most recently used task first, as it is
likely to be the one which is "closest" to a CPU (i.e. least likely to
be swapped out to disk).
Greetings,
Jacob
--
"Being an absolute ruler today was not as simple as people
thought. At least, it was not simple if your ambitions
included being an absolute ruler tomorrow."
next prev parent reply other threads:[~2012-12-12 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 13:53 Task with access to itself? Jacob Sparre Andersen
2012-12-05 14:18 ` Dmitry A. Kazakov
2012-12-05 16:57 ` Jeffrey Carter
2012-12-11 11:21 ` Jacob Sparre Andersen
2012-12-11 20:39 ` Jeffrey Carter
2012-12-12 20:25 ` Jacob Sparre Andersen [this message]
2012-12-12 21:11 ` Jeffrey Carter
2012-12-13 7:20 ` Jacob Sparre Andersen
2012-12-06 9:38 ` Egil Høvik
2012-12-06 19:53 ` Adam Beneschan
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox