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

Figure out why try_read_subscriptions() is so CPU intensive #2

Open
techtunde opened this issue May 14, 2022 · 0 comments
Open

Figure out why try_read_subscriptions() is so CPU intensive #2

techtunde opened this issue May 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@techtunde
Copy link
Collaborator

This repo was added to our company repo in an effort to add the try_read_subscriptions function to allow an immediately returning polling function for MQTT calls. When testing with vehicle software (which is where this is needed) the CPU usage of each hootl increased dramatically when compared to the existing way of polling MQTT deterministically (using timeout to not wait indefinitely), but this existing way has the potential for data loss.

@techtunde techtunde added the enhancement New feature or request label May 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant