-
Notifications
You must be signed in to change notification settings - Fork 21
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
How does Corece handle CPU-bound operations? #35
Comments
Hey @lucasmsoares96! Coerce uses the For this I would recommend using a library like Rayon, which offers a work-stealing thread pool: I can give you some examples on how you could achieve this with Coerce, if you'd like? Leon |
An example of this will help a lot! Thank you very much. |
I am migrating my project from actix to coerce and I have a question about how CPU-bound tasks are managed. The example below shows the actix code to perform the fibonacci operation on 3 Arbiters. An arbiter is a single-threaded event loop that runs one or more actors. In this way, although the event loop is blocked by the fibonacci calculation, it is possible to perform 3 calculations in parallel.
How does Coerce work under the hood? I couldn't find anything about it in the documentation. How to perform 3 CPU-bound tasks in parallel as in the example?
The text was updated successfully, but these errors were encountered: