rely in their prod deployment on
the implicit thread throttling so VT can just make them blow up so "easy"
in terms of code, hard in terms of tuning since them the actual throttling
was not planned anywhere else in the code I think.
That would make sense.
-chris
On 3/20/24 07:22, Raine
re.
>
Hmm, I have more than doubt. I currently have a case for a customer, we
scaled to the desired perf level tuning threads to a high number -
everything is old style and synchronous - but if we move to VT it will just
blow up and explode in mem in ~5s of load - tested a close approach.
So I
3/20/24 07:22, Rainer Jung wrote:
I wanted to share an observation and I hope the things are correct how
I
am describing them. Maybe things have already improved and I am not
aware of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
handle observability
ou pay for that is CPU usage. And most of us have CPU to spare.
-chris
Rainer,
Thanks for writing this up.
On 3/20/24 07:22, Rainer Jung wrote:
I wanted to share an observation and I hope the things are correct how I
am describing them. Maybe things have already improved and I am not
aware o
improved and I am
not aware of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
handle observability of virtual threads from inside the JVM and tooling.
The final outcome is, that virtual threads are not included in the
typical JVM APIs which one can use to
acktpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mer. 20 mars 2024 à 18:20, Christopher Schultz <
> > ch...@christopherschultz.net> a écrit :
> >
> >> Rainer,
> >>
> >> Thanks for writing this up.
>
ainer Jung wrote:
I wanted to share an observation and I hope the things are correct how I
am describing them. Maybe things have already improved and I am not
aware of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
handle observability of virtual threa
are an observation and I hope the things are correct how I
> > am describing them. Maybe things have already improved and I am not
> > aware of it, hints welcome.
> >
> > Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
> > handle observability
.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
handle observability of virtual threads from inside the JVM and tooling.
The final outcome is, that virtual threads are not included in the
typical JVM APIs which one can use to observe threads, like
enumerating them or
threads) discusses how to
handle observability of virtual threads from inside the JVM and tooling.
The final outcome is, that virtual threads are not included in the
typical JVM APIs which one can use to observe threads, like enumerating
them or accessing the stacks of individual threads. As a
mer. 20 mars 2024 à 13:11, Rainer Jung a
écrit :
Hi hi,
I wanted to share an observation and I hope the things are correct how I
am describing them. Maybe things have already improved and I am not
aware of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
han
à 13:11, Rainer Jung a
écrit :
> Hi hi,
>
> I wanted to share an observation and I hope the things are correct how I
> am describing them. Maybe things have already improved and I am not
> aware of it, hints welcome.
>
> Part of JEP 425 (Project Loom, Java virtual threads) d
Hi hi,
I wanted to share an observation and I hope the things are correct how I
am describing them. Maybe things have already improved and I am not
aware of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
handle observability of virtual threads from
13 matches
Mail list logo
