ScopedValue.runWhere not returning scope

[Marcin Grzejszczak]

> Definitely, yes. If you need to create a context for every virtual
thread, scoped values versus thread-local variables is the least of your
problems.

Can you elaborate please?

Pozdrawiam / Best regards,
Marcin Grzejszczak

https://marcin.grzejszczak.pl
https://toomuchcoding.com


czw., 13 cze 2024 o 19:23 Andrew Haley <aph-open at littlepinkcloud.com>
napisał(a):

> On 6/13/24 16:03, Robert Engels wrote:
> > 3. More importantly, if you use VT effectively, you are talking about
> > orders of magnitude more “trace contexts” (in the default brave handler
> > they are shared by thread so they are highly limited since the only
> > effective Java threading implementation prior to VT required pooled
> > threads) which reinforces my point about the increase in the volume of
> > unique data is the major problem for existing tracing libraries, which
> > will probably require architectural changes anyway.
>
> Definitely, yes. If you need to create a context for every virtual thread,
> scoped values versus thread-local variables is the least of your problems.
>
> --
> Andrew Haley  (he/him)
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> https://keybase.io/andrewhaley
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20240617/4147aa87/attachment.htm>