Romain,
On 3/20/24 16:25, Romain Manni-Bucau wrote:
Chris, added some comments inline.
Le mer. 20 mars 2024 à 19:41, Christopher Schultz <
ch...@christopherschultz.net> a écrit :
Romain,
On 3/20/24 13:34, Romain Manni-Bucau wrote:
Thread dumps being dump of threads - literally os threads -
Chris, added some comments inline.
Le mer. 20 mars 2024 à 19:41, Christopher Schultz <
ch...@christopherschultz.net> a écrit :
> Romain,
>
> On 3/20/24 13:34, Romain Manni-Bucau wrote:
> > Thread dumps being dump of threads - literally os threads - and virtual
> > threads not being threads at all
Am 20.03.24 um 18:50 schrieb Romain Manni-Bucau:
Le mer. 20 mars 2024 à 18:43, Rainer Jung a
écrit :
Am 20.03.24 um 18:34 schrieb Romain Manni-Bucau:
Hi Chris,
Thread dumps being dump of threads - literally os threads - and virtual
threads not being threads at all - they are runnables in a d
Romain,
On 3/20/24 13:34, Romain Manni-Bucau wrote:
Thread dumps being dump of threads - literally os threads - and virtual
threads not being threads at all - they are runnables in a dedicated thread
pool - it is quite fair to not make them the same and have their scheduler
- pool - only in the
Rainer,
On 3/20/24 13:33, Rainer Jung wrote:
Am 20.03.24 um 18:17 schrieb Christopher Schultz:
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 impro
Le mer. 20 mars 2024 à 18:43, Rainer Jung a
écrit :
> Am 20.03.24 um 18:34 schrieb Romain Manni-Bucau:
> > Hi Chris,
> >
> > Thread dumps being dump of threads - literally os threads - and virtual
> > threads not being threads at all - they are runnables in a dedicated
> thread
> > pool - it is q
Am 20.03.24 um 18:34 schrieb Romain Manni-Bucau:
Hi Chris,
Thread dumps being dump of threads - literally os threads - and virtual
threads not being threads at all - they are runnables in a dedicated thread
pool - it is quite fair to not make them the same and have their scheduler
- pool - only
Hi Chris,
Thread dumps being dump of threads - literally os threads - and virtual
threads not being threads at all - they are runnables in a dedicated thread
pool - it is quite fair to not make them the same and have their scheduler
- pool - only in the thread dump but not themselves no?
Similarly
Am 20.03.24 um 18:17 schrieb Christopher Schultz:
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 of it, hints welcome.
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 of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual thread
Thanks Romain,
I am well aware of the limits oof this attempt concerning async
processing. Still lots of applications can still be diagnosed with this
methodology and I am a bit frustrated, that project loom simply dropped
support for thread inspection via JMX and as a replacement provided a
Hi Rainer,
Think this is not related to virtual threads I think and way older (2010?).
Since some years we use AsyncContext and therefore thread dumps don't match
pending requests but just active computation (you can get 8K requests with
8 threads for ex).
Most of the sync instrumentation (assumpt
12 matches
Mail list logo