Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming.threads > #504

Coroutines and threads

Show all headers | View raw

Group,
I recently came across a call processing module design, where each call 
was handled by a coroutine/fiber that were fired on different threads. 
Whenever, a coroutine has to make a blocking call it will sleep. At a 
heavy load, software is likely to make millions of coroutines.  If I 
were to design such a system, I would process it through thread only (no 
coroutines) by making the call non-blocking, whenever call is waiting 
for some event, I will store the callcontext in a hash/map and start 
executing next call.

I also came across google go language that supports goroutines similar 
to coroutine and CSP. Google also claim that they are heavily using it 
for development inside google.

Do you see any case for using coroutines, except possibly, atleast in 
the above example, you will not require state machine and its call 
context data base if you use coroutines.
thanks
Ittium

Back to comp.programming.threads | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Coroutines and threads ittium <ittium@gmail.com> - 2011-08-11 11:20 +0530
  Re: Coroutines and threads naveen <naveenkumarkaushik@gmail.com> - 2011-08-12 02:40 -0700

csiph-web