-
Notifications
You must be signed in to change notification settings - Fork 154
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 adding custom dispatchers #207
Comments
You mean something else than?
|
something like:
|
But isn't point that that Configurator can produce a custom dispatcher/executor? https://gist.github.com/yanns/f7da61c582ab1da3535d#file-gistfile1-scala-L41 |
thanks - that gist looks like a good example - maybe we should include something like that in the Pekko docs |
it's currently using the fork join pool, maybe we can change that as CE to include a WSTP。 |
The what from the what now? Anyhow, using the fork join pool is also about the interaction with the scala.concurrent.blocking code block of course. |
Akka/Pekko may already have a mechanism for adding custom dispatcher implementations. I just haven't found anything obvious.
With Java Virtual Threads, it would be nice if an external party could create a custom dispatcher that uses throwaway virtual threads instead of pooling them.
The text was updated successfully, but these errors were encountered: