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

Experiment: Timing System #660

Open
pathunstrom opened this issue Feb 3, 2022 · 0 comments
Open

Experiment: Timing System #660

pathunstrom opened this issue Feb 3, 2022 · 0 comments
Labels
The Future Tickets revolving around the future direction of ppb.

Comments

@pathunstrom
Copy link
Collaborator

Regarding a conversation between myself and @AstraLuma, we discussed a more robust methodology for allowing PPB to be run by external event loops. One of the things we should test first is how systems function when they are no longer driving their own signalling system.

Primary targets for this experiment:

Updater will become our intermediary timer. It needs to grow a few capabilities: one time timeouts (use the event system both ways), and a "wait" function the engine will call for the sleep. Hopefully what this does is make the engine use a lot less CPU resources without sacrificing performance.

If this experiment is successful, we can discuss out to externalize this from the engine itself/fold these functions into the engine for a default implementation.

@pathunstrom pathunstrom added the The Future Tickets revolving around the future direction of ppb. label Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
The Future Tickets revolving around the future direction of ppb.
Projects
None yet
Development

No branches or pull requests

1 participant