# Insights scales
**URL:** https://community.homey.app/t/insights-scales/16579
**Category:** Questions & Help
**Created:** [August 8, 2019, 7:32am UTC](https://community.homey.app/t/insights-scales/16579 "2019-08-08T07:32:47Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Rickp](https://community.homey.app/u/Rickp)
#### Post date: [August 8, 2019, 7:32am UTC](https://community.homey.app/t/insights-scales/16579/1 "2019-08-08T07:32:47Z")
I’m looking into some insights and am a bit confused by the scale it works with. Looking at average system load it goed from 0 to ± 2.5. So is for example “1” equal to 1%, or 10%, or is 1 “full load” and everything above overload? The last would make the most sense in my case.
Is there Anyway to format the scales within the insights pages (so no exported data)
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [August 8, 2019, 7:41am UTC](https://community.homey.app/t/insights-scales/16579/2 "2019-08-08T07:41:59Z")
> [@Rickp](#):
>
> Looking at average system load it goed from 0 to ± 2.5. So is for example “1” equal to 1%, or 10%, or is 1 “full load” and everything above overload? The last would make the most sense in my case.
You are correct: 1 means “full load”, and everything above it means your system is overloaded. A load of 2.5 means that (on average) 2.5 processes are waiting to be assigned a CPU time slice.
It’s a bit confusing that in Insights, the “load average” value is used (where 1 = full load), but in the mobile Homey app, a percentage is used (which, AFAIK, is basically the load value \* 100).
> [@](#):
>
> Is there Anyway to format the scales within the insights pages (so no exported data)
I don’t think there is.
---
### Author:  [@Rickp](https://community.homey.app/u/Rickp)
#### Post date: [August 8, 2019, 7:50am UTC](https://community.homey.app/t/insights-scales/16579/3 "2019-08-08T07:50:30Z")
Quite odd that there are so much spikes during the night, but the part between 0800 & 0900 explaines why things don’t go smooth, or not happening at all.
Time to try and shed some more weight while athom makes a backup and restore function so I can move to a homey pro or even better a homey 2.
Tnx
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [August 8, 2019, 7:54am UTC](https://community.homey.app/t/insights-scales/16579/4 "2019-08-08T07:54:00Z")
I also see a fair amount of spikes, I think that Homey’s core periodically does housekeeping at those times.
You could try to correlate those spikes to specific apps (although, again, it’s confusing that for apps, CPU usage graphs are incremental, meaning that instead of looking for peaks, you need to look for sharp increases).
---
### Author:  [@Rickp](https://community.homey.app/u/Rickp)
#### Post date: [August 8, 2019, 8:13am UTC](https://community.homey.app/t/insights-scales/16579/5 "2019-08-08T08:13:22Z")
Yeah have been looking but there is no real correlation te be found. The spike of above 2 can be explained. A door was opened while the alarm was armed and then a bunch of things should happen like turning on all lights (different manufactuors) , wich have always been a bit heavy for homey. Now however it was more miss then hit, wich is the second time now.
I’ll make this a bit lighter by removing the fancy parts wich are not strictly neccesary.
---
### Author:  [@Kyrcio](https://community.homey.app/u/Kyrcio)
#### Post date: [August 8, 2019, 4:46pm UTC](https://community.homey.app/t/insights-scales/16579/6 "2019-08-08T16:46:37Z")
> [@robertklep](#):
>
> It’s a bit confusing that in Insights, the “load average” value is used (where 1 = full load), but in the mobile Homey app, a percentage is used (which, AFAIK, is basically the load value \* 100).
Also, load average != CPU usage. Load average is the pressure on the scheduler, where 1 means it can execute as much as is being scheduled on one core. CPU usage is how much of a cores time is spent in each state. A single core machine can’t have a CPU usage higher than 100%, but it can have a load average much higher than that. I am not sure if load average ~ CPU usage for values much lower than the number of cores, but it is definitely not so for values close to or above the number of cores.
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [August 8, 2019, 4:52pm UTC](https://community.homey.app/t/insights-scales/16579/7 "2019-08-08T16:52:47Z")
Both the percentage values and the values shown in the Insights graphs are based on the load average (where using % as a unit makes no sense as I’ve tried to explain to Athom once, but they don’t particularly care).
The Insight graphs for apps are even more confusing, because they use % as a unit but are based on some sort of incremental metric (the graphs always go up), which, I assume, it based on CPU _time_. However, how that value is translated to a percentage, I don’t know.
---
### Author:  [@Eko\_taas](https://community.homey.app/u/Eko_taas)
#### Post date: [January 29, 2024, 9:19pm UTC](https://community.homey.app/t/insights-scales/16579/8 "2024-01-29T21:19:41Z")
Same subject, but diff. angle of scaling…
Is there any way I could impact insight scale (only issue with web, android app OK) - e.g. here 9.0 when clearly off (actual trend value have 4 decimals)
Trend values from AVD / number fields if makes difference somehow…
---
### Author:  [@Eko\_taas](https://community.homey.app/u/Eko_taas)
#### Post date: [February 16, 2024, 5:20am UTC](https://community.homey.app/t/insights-scales/16579/9 "2024-02-16T05:20:25Z")
Just in case some bothered with same issue (to close the loop): When creating trend, take the 1st items with desired desimals defined. Seems that scale always based on 1st one (only)…