C4 hub running 22.214.171.124 but this has been occuring with a few of the previous releases as well..
Simply put this is a dev C4 that doesn't do much. Really all it does is run Ecobee Suite, Chromecast integrations, and maker API with 3 devices. It has been running fine for probably a month and even early initial 2.2.8 releases.
Recently I added a new flow to Node Red and created a Virtual UPS driver to the hub. The flow is designed to only send updates when needed, but a few items on the device do update frequently. Also the data provider for Node red requires a 10 sec Inject. The flow is adjusted to prevent repeat updates to Hubitat as much as possible. Most items that don't update have a deduplication step to prevent multiple submits to Hubitat. The 3 items that change frequently have been updated to run from a single stream submited the change once every 10 seconds.
Well the point of all this though is to ask the question why the C4 is getting hammered with CPU Load when this flow is running. The device driver doesn't show any high CPU in runtime stats. All it does is post the change from the command via maker api calls. But the hub shows sever CPU Load. This is clearly related to this UPS data from Node-Red via Maker API because if i disable the updates from Node-Red it the CPU issues seem to go away.
Does the system really struggle with 3 updates to 1 device every 10 seconds.