Increased CPU usage after updating to 8.2.0
ScottG489 opened this issue · 14 comments
Problem/Motivation
Stark increase in CPU usage after updating to 8.2.0. I have CPU usage information since the beginning of the year:
And confirmation this is right after I updated:
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!
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!
Still observing the same higher sustained usage.
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!
Still observing higher sustained usage. However, since v8.2.2 it seems to have dropped a bit, though still magnitudes higher than before.
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!
No change since my last update.
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!
Still an issue.
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!
Still an issue.
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!
Still an issue.
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!
Since originally reporting it's come back down once (one is due to hardware upgrades on my end):
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.