hassio-addons / addon-grafana

Grafana - Home Assistant Community Add-ons
https://addons.community
MIT License
213 stars 61 forks source link

Increased CPU usage after updating to 8.2.0 #312

Closed ScottG489 closed 8 months ago

ScottG489 commented 1 year ago

Problem/Motivation

Stark increase in CPU usage after updating to 8.2.0. I have CPU usage information since the beginning of the year:

Screen Shot 2023-03-16 at 2 15 02 PM

And confirmation this is right after I updated:

Screen Shot 2023-03-16 at 2 16 54 PM

Looking at the numbers, it looks like it went from using on average .2% usage to 2.5% which is fairly significant.

Although relatively it's a large increase, overall it's pretty small on my particular machine. I still thought it might be worth posting here in case anyone else may have been impacted more on their system.

Expected behavior

For the CPU usage to stay relatively the same before and after the update. Or for there to at least have been some documentation in the release notes that this effect would be present on users systems after the update.

Actual behavior

Large increase in usage relative to before the update. May be fine for most users, but it may have been a good idea to point this out in the release notes.

Steps to reproduce

Update to version 8.2.0 from 8.1.0.

I can't comment on historical CPU usage before 8.1.0 since my data only goes back to when I had this installed.

Restarting the add-on doesn't have an effect on sustained usage.

Proposed changes

Perhaps integrating some performance tests into the CI pipeline? \ \ Otherwise, thanks for maintaining a great add-on!

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 1 year ago

Still observing the same higher sustained usage.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 1 year ago

Still observing higher sustained usage. However, since v8.2.2 it seems to have dropped a bit, though still magnitudes higher than before.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 1 year ago

No change since my last update.

github-actions[bot] commented 12 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 12 months ago

Still an issue.

github-actions[bot] commented 11 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 11 months ago

Still an issue.

github-actions[bot] commented 9 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 9 months ago

Still an issue.

github-actions[bot] commented 8 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ScottG489 commented 8 months ago

Since originally reporting it's come back down once (one is due to hardware upgrades on my end):

Screenshot 2023-10-24 at 12 55 16 PM

Seems to still be roughly twice the usage as before, but given the absolute usage is pretty insignificant and no one seems to be having an issue, I'm going to close this.

It'll still be around for historical reference in case anyone else runs into problems.