what's the difference between thread sheduling actor and thread context
switch
it is said in scala that using the actors can scale much better compared
with traditional threading. I can understand that bit like keep thread
blocking is obiviously not good. but what is the difference of thread
scheduling new tasks and thread context switches? isn't this kind of
scheduling new tasks will incur performance penalties as well ?
similar scenario in .NET as well, the async does similar things, I don't
understand the difference here of the thread switching off from the state
machine switching on to the unfinished tasks with context switches happen
on threads, after all what's the difference ?
No comments:
Post a Comment