-
Couldn't load subscription status.
- Fork 20
Some component status cleanup #839
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
Conversation
There's going to be status trackers for more component types. Those can now go into the `_component_status` package. Signed-off-by: Sahas Subramanian <[email protected]>
When constructing `ComponentPoolStatusTracker` objects. Signed-off-by: Sahas Subramanian <[email protected]>
In the component status tracking parts of the power distributor. Signed-off-by: Sahas Subramanian <[email protected]>
Signed-off-by: Sahas Subramanian <[email protected]>
Signed-off-by: Sahas Subramanian <[email protected]>
|
Only internal improvements, no release notes necessary. |
d0d6867 to
97e59b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! I'm just curious about Use a cached zero duration value, instead of repeatedly allocating, did this showed up in some benchmark?
no, but they do allocate in the hot path, which is many times slower than referencing a cached value. |
|
Yeah, creating objects is really slow. Not sure if there will be any caching going on when creating the same (immutable) object over and over though. |
timedeltas instead offloats for duration in component status trackers.ComponentStatusTrackers intoBackgroundServices