[concurrency-interest] ForkJoinPool for async http calls?

√iktor Ҡlang viktor.klang at gmail.com
Fri May 11 10:55:04 EDT 2012


On Fri, May 11, 2012 at 9:46 AM, Mark Thornton <mthornton at optrak.com> wrote:

> On 11/05/12 04:03, Zhong Yu wrote:
>
>>
>> Yes thread-per-connection doesn't work, today. My question is, could
>> OS/VM do some optimization to make it work? Or there are reasons
>> prohibiting that?
>>
>>
> There have been VMs designed to run tens of thousands of threads even in a
> 32 bit system. One of the critical resources in a VM like HotSpot is the
> address reserved for each thread's stack. Typically this is 256K in a 32
> bit system. This clearly limits the number of threads you can have. I
> remember a VM which allocated much smaller stacks initially (8K perhaps)
> and then expanded the stack if it became full  (expensive, but hopefully
> rare). The rationale here was to permit the one thread per connection model
> to scale to very large numbers of connections


10s of thousands is still a low number though. We currently run ~2.5
million Actors per GB of heap.

Cheers,
√



>
>
> Mark Thornton
>
>
> ______________________________**_________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.**oswego.edu <Concurrency-interest at cs.oswego.edu>
> http://cs.oswego.edu/mailman/**listinfo/concurrency-interest<http://cs.oswego.edu/mailman/listinfo/concurrency-interest>
>



-- 
Viktor Klang

Akka Tech Lead
Typesafe <http://www.typesafe.com/> - The software stack for applications
that scale

Twitter: @viktorklang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20120511/5c661bb2/attachment-0001.html>


More information about the Concurrency-interest mailing list