[External] : Re: jstack, profilers and other tools

[eric at kolotyluk.net]

The way I look at it now, if operations are blocking, then creating more Virtual Threads creates more opportunities for unblocked code to run.

In the past, we could not create enough Platform Threads to create such opportunities, and we had to rely on non-blocking patterns, such as Reactive programming. Akka/Scala demonstrated this years ago as being very effective.

Loom simply allows us the same power of concurrency, without having to follow non-blocking patterns…

 

Cheers, Eric

 

From: loom-dev <loom-dev-retn at openjdk.org> On Behalf Of Pedro Lamarão
Sent: July 15, 2022 7:05 AM
To: Alex Otenko <oleksandr.otenko at gmail.com>
Cc: Ron Pressler <ron.pressler at oracle.com>; loom-dev <loom-dev at openjdk.java.net>
Subject: Re: [External] : Re: jstack, profilers and other tools

 

Em sex., 15 de jul. de 2022 às 05:39, Alex Otenko <oleksandr.otenko at gmail.com <mailto:oleksandr.otenko at gmail.com> > escreveu:

 

Adding threads allows to do more work. But you can't do more work at will - the amount of work going through the system is a quantity independent of your design.

 

I think that, more precisely, the maximum amount of work that can go through a concrete system is a quantity independent of programmer design.

Nobody is arguing that increasing the quantity of threads will increase work throughput in a machine with devices already at full capacity.

What is being argued is that, since "task" is one of the machine's "devices" consumed to do work, 

increasing the capacity for "tasks" increases the maximum amount of work that can go through etc.

If there are free processors, free memory, free network bandwidth, free storage bandwidth etc. etc. then doing more work concurrently will increase work throughput.

 

-- 

Pedro Lamarão

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20220715/d065fbbd/attachment.htm>