The future of concurrent programming

[Sean Kelly]

Jeff Nowakowski wrote:
> Sean Kelly wrote:
>> Because context switching is expensive.  Running thousands of threads 
>> on a system with only a few CPUs may use more time simply switching 
>> between threads than it does executing the thread code.
> 
> Did you look at the throughput in the graph I linked to?  Erlang has 
> it's own concept of threads that don't map directly to the OS.  Look again:
> 
> http://www.sics.se/~joe/apachevsyaws.html

Sorry, I misundertood.  For some reason I thought you were saying Apache 
could scale to thousands of threads.  In any case, D has something 
roughly akin to Erlang's thread with Mikola Lysenko's StackThreads and 
Tango's Fibers.


Sean