Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage of 2.3.0 vs. 2.2.0 (3 times) #181

Open
j64bit opened this issue May 6, 2023 · 4 comments
Open

High CPU usage of 2.3.0 vs. 2.2.0 (3 times) #181

j64bit opened this issue May 6, 2023 · 4 comments
Labels
enhancement ⬆️ New feature or request

Comments

@j64bit
Copy link

j64bit commented May 6, 2023

Describe the bug
On my raspi 4 version 2.3.0 uses 28% CPU, where version 2.2.0 uses only 7.5%.

To Reproduce
iobroker allows to up and downgrad as well.
I use telegraf and chronograf to track cpu usage per process.

Expected behavior
Ideally the CPU usage should stay a 7.5%.

Screenshots & Logfiles
grafik

Versions:

Additional context

@klein0r klein0r added the enhancement ⬆️ New feature or request label May 8, 2023
@klein0r
Copy link
Contributor

klein0r commented May 8, 2023

There were not that many changes between 2.2.0 and 2.3.0. What types of statistics do you use?

@j64bit
Copy link
Author

j64bit commented May 9, 2023

Thanks for looking at the topic and also many thanks for creating this adapter - it is very helpful.

The highest frequency data is around 10 parameters that are updated every second from the PV system.
These use averaging statistics, only. (which includes daily values, which i need as well)

These is two parameters with around 1 update per 5 minutes, which use counting type.

@klein0r
Copy link
Contributor

klein0r commented May 9, 2023

These use averaging statistics, only.

Maybe that is related to

* (klein0r) Added hourly, weekly, monthly, ... averages

That could lead to higher CPU usage. I will test that

@j64bit
Copy link
Author

j64bit commented May 9, 2023

Great, thanks. Please let me know if can help at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ⬆️ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants