On Tue, Nov 11, 2008 at 5:57 AM, davy zhang <da*******@gmail.comwrote:
first here is my basic idea is every actor holds their own msg queue,Using stackless, every tasklet can have a channel which it uses to communicate
the process function will handle the message as soon as the dispatcher
object put the message in.
with other tasklets. The tasklet is blocked until there's something on
the channel
to receive.
This idea naturally leads me to place every actor in a separate threadYou can have actors with many separate tasklets waiting for messages, still
waiting for msg
being relatively lightweight, meaning you can run thousands of tasklets without
serious lack of performance.
but I found the tasklet is really a lined-up sequence , that means ifThis is cooperative scheduling, which you can choose not to use with Stackless
a tasklet blocked or do some time consuming calculation, the other
tasklets can not get the cpu slice
(instead, use preemptive scheduling). If you determine that one particular
task is taking too much cpu, you can declaratively call stackless.schedule()
and put that task back to the scheduler queue and allow other tasks to
have a go.
so we must design very carefully to avoid the big job for single taskThat's right - with cooperative scheduling careful design is the key.
I am just confused why the stackless python is said to be good atStackless is an extremely lightweight way into concurrent programming.
concurrency program model or just I get a wrong idea to practice?
I have personally used it in few projects and i quite like how lightweight
it is and how easy it is to write concurrent programs.
On the plus side, Stackless developers have plenty of examples and
common idioms of how Stackless should be used, which I highly recommend
you to check out. You might find a solution to your problem right there
amongst the examples.
Check it all out on http://www.stackless.com
--
a lex 13 x
http://www.a13x.info
