<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">I didn’t say it wasn’t possible - I’m saying forcing the designer to figure out “this runs here and that runs there” has scalability problems for large systems (not microsevices). Having better support in vthreads would be great - but certainly not required. </div><div dir="ltr"><br><blockquote type="cite">On Jan 6, 2023, at 12:40 PM, Ron Pressler <ron.pressler@oracle.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 6 Jan 2023, at 16:37, Robert Engels <<a href="mailto:rengels@ix.netcom.com" class="">rengels@ix.netcom.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="auto" class="">
<div dir="ltr" class=""></div>
<div dir="ltr" class="">I have to agree a bit with Arnaud. I don’t like the idea that I have to “reason about” these issues.
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">I’m not asking anyone to reason about any issue. I am asking people to report any problem they run into, as that is extremely valuable feedback and could help us a lot.</span></font></div>
<div><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class="">
</span></font></div>
<div><font color="#000000" class="">Reporting a hypothetical problem that people have *not* run into is not particularly useful, not because the problem cannot manifest in reality, but because I don’t know how to solve a hypothetical problem (how would I know
that I’ve solved it)? There’s just nothing we can do with that discussion (and these are all things we’ve thought about for years, but because we haven’t been able to observe them, we obviously haven’t been able to address them). </font></div>
<div><font color="#000000" class=""><br class="">
</font></div>
<div><font color="#000000" class="">I just don’t know how to fix a non-bug. We could add, say, a 10ms time slice, but would that really fix a problem that we haven’t seen yet? How would we know that the non-bug has been fixed before if no one encounters the
bug? </font></div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="auto" class="">
<div dir="ltr" class="">Imagine a server service that encodes video. Highly cpu bound. But then a need to emit heartbeats to keep clients alive. I have to know “put heartbeat requests on their own native thread” because too many client encoding requests will
cause them not to be sent. Or even more simply - a very short encoding request takes a very long time because it is blocked by other long running requests that got there first. FIFO doesn’t lead to the best user experience at times. </div>
<div dir="ltr" class=""><br class="">
</div>
<div dir="ltr" class="">With timeslicing and fairness that can be avoided. </div>
<div dir="ltr" class=""><br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">Yes, but there’s a much better way to do this than by adding timesharing to virtual threads: run your encoding service on platform threads.</div>
<div class=""><br class="">
</div>
<div class="">— Ron</div>
<div class=""><br class="">
</div>
</div></blockquote></body></html>