[MUD-Dev] Event Scheduling

Phillip Lenhardt philen at funky.monkey.org
Thu Feb 10 12:01:23 New Zealand Daylight Time 2000

On Tue, Feb 08, 2000 at 10:31:39AM -0800, J C Lawrence wrote:
> The general intent is that only a small minority of the total number 
> of "events" will ever actually invoke the queing system, and that,
> further, due to the size and processing capacity of the Executor's
> thread pool, that the pool of events awaiting execution by threads,
> will always be small.

As someone has mentioned, short-circuiting your queue means that queued
events are running at a lower priority than events that bypass the queue.
That is not necesssarily bad, but I find it undesireable. Adding a flag to
events such that if the flag is set, it bypasses the queue seems like a
better solution (ie marking some events "real-time").

> My bottlenecks are on physical IO, not compute, so I don't tend to
> worry much about these aspects too hard beyond chosing reasonable
> algorithms.

In Moebius, our bottlenecks all seem to be in the interpreter, so in our
case, choosing the absolute best algorithms and data structures/models can
make all the difference in the world.

MUD-Dev maillist  -  MUD-Dev at kanga.nu

More information about the MUD-Dev mailing list