This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Exactly what does CPU/IO measure, and how can you lower it?
#2
Occasional load average spikes are nothing to worry about. If you constantly have load over 0.7 then something can probably be optimized.
SD card writes do not happen often to preserve the card's lifespan. The usual sync interval is 30 minutes.

A) using grp.checkupdate() rather than grp.update()
This can be helpful for many updates and when KNX/IP Routing is used. But this mostly applies to grp.write() because KNX/TP bus can be easily overloaded.

B) avoid scheduling scripts to run at the exact same time
Only if scripts are doing some heavy computations.

C) refactoring large user libraries, and break large files down into many smaller files
Does not affect the system load much.

D) avoid 5-minute trends
Does not affect the system load much.

E) avoid using more than ??? trends in total (any upper limit?)
The more trends you have the more calculations have to be done on the data. This happens once every minute.
Reply


Messages In This Thread
RE: Exactly what does CPU/IO measure, and how can you lower it? - by admin - 09.04.2024, 07:30

Forum Jump: