<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 11/07/2022 22:13, Rob Bygrave wrote:<br>
<blockquote type="cite" cite="mid:CAC=ts-EgN=YfP=wsMMbqZ2HwGydkz83TY5b=5zA0vqm1K1Cszg@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">:</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">> <i><b>unusual</b></i> for an application
that has any virtual threads to have fewer than, say, 10,000</div>
<div><br>
</div>
<div>In the case of http server use of virtual thread, I feel
the use of <i><b>unusual</b></i> is too strong. That is, when
we are using virtual threads for application code handling of
http request/response (like Jetty + Loom), I suspect this is
frequently going to operate with less than 1000 concurrent
requests per server instance. <br>
</div>
<br>
</div>
</blockquote>
I think the interesting thing is that those 1000 concurrent requests
can be handled by code that is written to do blocking operations
without having to resort to writing asynchronous code. It may be
that the handling of these requests will "fan out" where the work in
the handler splits into several sub-tasks and each sub-task running
in its own virtual thread. In that scenario there will be a lot more
threads.<br>
<br>
-Alan<br>
</body>
</html>