-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Virtual Thread Dispatcher for Pekko Projections #233
Comments
I don't understand why we would want to support a non-blocking dispatcher here. |
Don't you think that since the Event Handlers need to persist into the database (blocking operation), we may benefit from using Virtual Threads since blocking on I/O doesn't block the OS Thread? If we wanted to try using Virtual Thread Threads, do you suggest specifying our own dispatcher definition with the executor set to Edit: I've tried adding the above, but it doesn't seem to be working. Here goes a snippet of my conf:
|
I answered this in #233
|
I've updated one of my comments above. But, in any case, here a snippet of my conf for projections. I've tried investigating what type of thread is executing inside the projection handler and it seems as though it's not a Virtual Thread.
|
I had a quick look at the code and I can't see anything that would prevent this from working. There are no logs or reproducible test cases to back the assertion that it doesn't work. I may have time later in the week to try to test this myself. |
Currently, Pekko Projections only support the
blocking-jdbc-dispatcher
(see https://pekko.apache.org/docs/pekko-projection/current/jdbc.html). Are there any plans to start supporting a new dispatcher that uses Virtual Threads, similar to what has been achieved in the standard actor dispatcher ?The text was updated successfully, but these errors were encountered: