You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@polaris.apache.org by "jbonofre (via GitHub)" <gi...@apache.org> on 2024/10/29 17:22:33 UTC
[I] Use VirtualThreads for Polaris TaskExecutor [polaris]
jbonofre opened a new issue, #411:
URL: https://github.com/apache/polaris/issues/411
### Is your feature request related to a problem? Please describe.
_No response_
### Describe the solution you'd like
_No response_
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
--
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: issues-unsubscribe@polaris.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Use VirtualThreads for Polaris TaskExecutor [polaris]
Posted by "eric-maynard (via GitHub)" <gi...@apache.org>.
eric-maynard commented on issue #411:
URL: https://github.com/apache/polaris/issues/411#issuecomment-2450524979
Agreed that we should look into optimizing this, though I don't know enough about virtual threads to have a strong opinion about the implementation. @snazy's concerns above seem valid.
Long-term, I am hoping that @flyrain's recent [proposal](https://docs.google.com/document/d/1Pd_mzZcfvnUvcH98IbwsIYf4eryet1lQDfclKYx-t-M/edit?tab=t.0#heading=h.7ic5c343eju1) will let us fully delegate this kind of work to an external service and make this problem moot.
--
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: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Use VirtualThreads for Polaris TaskExecutor [polaris]
Posted by "snazy (via GitHub)" <gi...@apache.org>.
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: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org