snazy commented on issue #411:
URL: https://github.com/apache/polaris/issues/411#issuecomment-2446634631
IMHO we should be really careful with Java virtual threads, because those
are not a "just turn it on and everything's faster & better" thing. VTs come
with quite some fine-print. In a nutshell: everything that runs on a VT
**must** meet a bunch of criteria - otherwise the stability of the whole
process is at risk, likely not in every environment ("number of CPUs").
Few posts that discuss this topic:
* [Quarkus - five things to know before using
VTs](https://quarkus.io/blog/virtual-thread-1/#five-things-you-need-to-know-before-using-virtual-threads-for-everything)
* [Oracle - practical
advice](https://docs.oracle.com/en/java/javase/20/core/virtual-threads.html#GUID-4A63E9EA-B16A-4633-87D8-C3DC08A3277C)
* [Netflix - locking issues w/
VTs](https://netflixtechblog.com/java-21-virtual-threads-dude-wheres-my-lock-3052540e231d)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
