[concurrency-interest] Blocking vs. non-blocking

Vitaly Davidovich vitalyd at gmail.com
Wed Aug 6 16:43:01 EDT 2014


:) Erlang is a different matter altogether.  If you have a runtime with
fibers/coroutines, knock yourself out.

Sent from my phone
On Aug 6, 2014 4:39 PM, "Raoul Duke" <raould at gmail.com> wrote:

> > If you were going to do a thread-per-request model, what would happen if
> you
> > have 100k+ connections? I'm not aware of any OS that can handle that many
> > threads (even if only a small fraction of them is runnable, that's going
> to
> > be a fairly chunky absolute number).  Memory footprint will be an issue
> as
> > well, especially if the stack sizes get big.
>
> oh come on, you've never heard of a company that got bought for $19
> billion in stock by facebook, or the stack they use? :-}
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20140806/02f63366/attachment.html>


More information about the Concurrency-interest mailing list