I'm not having any hub slowdown issues, but want to prevent any in the future.
I notice a few apps under app stats have quite a bit of what I assume is processor time (in miliseconds).
My top apps are echo speaks (19,000,000ms) and ecobee suite (3,100,000ms). The hub has been up for just over 4 days.
Under device stats, my echo devices are all the top users with over 1 million ms. A few devices like switches are around 500,000.
Is that excessive or anything to worry about, and am I interpreting the time values correctly?
So there are 86,400,000 milliseconds per day, 4 days = 345,600,000.
22,100,000/86,400,000 = roughly .064 or 6.4% usage by the apps
Don't think you have an issue....
Makes sense. Basically if the hub had 24 hours uptime, and 86,400,000 ms total between all apps would be the CPU being pegged for that 24 hours.
You got it, a real quick check is to add the local apps percentage reported to the device percentage reported to determine a ballpark total % busy.
The total from the top above the header?
Local apps: 6h 54m 10s (7.0%)
Devices: 12h 54m 14s (13.1%)
So in my case I'm averaging 20ish percent. Doesn't seem bad. Just wanted to check in and make sure I'm not going too crazy on apps and killing my hub.
Yeah, at 20% your hub is coasting....
2 Likes
Also if your apps load is running at 7.0% and you have an app taking 20% of it, the app is taking just under 2% of the total load.
3 Likes
This is very useful. I wasn't sure how to interpret these numbers either. One question though. The Device/Apps Stat page also has a bit of info on "Uptime" Mine shows:
Uptime: 2254d 19h 45m 29s
I wonder if I should shut it down and give this poor baby a rest.
6 years might be a little much...
Well I am calling the business I bought this hub from and demanding a refund. I have only had the hub since January
Seriously though, I assume this is a bug?
1 Like
BiGs
March 4, 2021, 8:59pm
12
Mine:
Uptime: 2254d 20h 57m 13s
No way.
aaiyar
March 4, 2021, 9:23pm
13
Possibly. Another scenario could be where the HE couldn't find an NTP server during boot when the log started, setting the default time to be 6 years ago. An NTP server was found later - so more recent logs give the impression your HE has been up for 6 years and spare change.
1 Like
Mine says
Local apps: 0h 57m 22s (0.1%)
Devices: 0h 0m 6s (0.0%)
I guess I'm ok
My app stats look like below. Are my Echo speaks and combined presence taking too much CPU time? If yes, can i optimize that somehow?:
aaiyar
September 3, 2021, 9:38pm
16
Repeat this screenshot with "Total time hub spent processing app code" also selected.
1 Like
0.15% of the total available, or about 2 1/3 minutes out of 26, practically standing still. Apps don’t appear to be an issue. What does the device tab look like?
