Skip to content
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

refactor(framework) Introduce double queue mechanism for Simulation Engine #3468

Merged
merged 52 commits into from
Jul 10, 2024

Conversation

jafermarq
Copy link
Contributor

Workers in the Simulation Engine never interface directly with the State. Instead, they get a TaskIns from a queue and put the TaskRes into another. Two auxiliary coroutines (will be converted to vanilla Threads later) interface between State and the respective queue.

@jafermarq jafermarq added the simulation An issue related to Flower's simulation label May 19, 2024
@jafermarq jafermarq changed the base branch from main to use-inmemory-driver-in-simulations May 19, 2024 14:38
Base automatically changed from use-inmemory-driver-in-simulations to main May 19, 2024 15:53
@jafermarq jafermarq marked this pull request as ready for review June 11, 2024 12:50
@danieljanes danieljanes merged commit a9795a4 into main Jul 10, 2024
28 checks passed
@danieljanes danieljanes deleted the simplify-sim-double-queue branch July 10, 2024 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
simulation An issue related to Flower's simulation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants