[concurrency-interest] Benchmark to demonstrate improvement in thread management over the years.
nathan.reynolds at oracle.com
Tue Aug 13 13:12:05 EDT 2013
An event model requires copying the state into heap objects. A thread
model allows the state to stay on the stack. So, an event model may be
able to reuse the threads but puts more pressure on the heap and GC.
HotSpot's escape analysis is trying to reduce heap pressure by putting
more objects on the stack. However, there is a cost for having the
stack. The hard question is which costs more.
On 8/12/2013 7:06 AM, Oleksandr Otenko wrote:
> On 12/08/2013 14:03, Unmesh Joshi wrote:
>> Most of the books on node.js, Akka, Play or any other event IO based
>> system frequently talk about 'Threads' being heavy and there is cost
>> we have to pay for all the booking the OS or the JVM has to do with
>> all the threads.
>> While I agree that there must be some cost and for doing CPU
>> intensive tasks like matrix multiplication, and fork-join kind of
>> framework will be more performant, I am not sure if for web server
>> kind of IO intensive application that's the case.
>> On the contrary, I am seeing web servers running on tomcat with 1000
>> + threads without issues. For web servers. I think that Linux level
>> thread management has improved a lot in last 10 years. Same is with
>> the JVM.
>> Do we have any benchmark which shows how much Linux thread management
>> and JVM thread management have improved over the years?
>> Concurrency-interest mailing list
>> Concurrency-interest at cs.oswego.edu
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest