You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The need for state_changed_on being set for metrics collection purposes is causing performance issues for refresh because the custom raw_power_state= method must be invoked in ruby code and cannot be processed by batch saving.
If there were another way to detect gaps in metrics data or remove the detection entirely then the state_changed_on column would no longer be needed.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated for at least 6 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
The need for state_changed_on being set for metrics collection purposes is causing performance issues for refresh because the custom
raw_power_state=
method must be invoked in ruby code and cannot be processed by batch saving.If there were another way to detect gaps in metrics data or remove the detection entirely then the state_changed_on column would no longer be needed.
The text was updated successfully, but these errors were encountered: