Set low latency to false to avoid CPU spike - #189
Merged
Conversation
Owner
|
Thank you, that indeed sounds like a better default! |
Owner
|
Its released as 1.11.1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am impacted by home-assistant/core#173474 in which high CPU usage was reported since 2026.6.0
The low latency flag was the culprit which defaults to True if not explicitly provided.
Forcing low_latency = False when calling create_serial_connection method of serialx solves the problem for me and /sys/bus/usb-serial/devices/ttyUSB0/latency_timer stays at 16
Tested with 2026.7.1 and latest release of this package.