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

Proxmox VE integration: (very) high CPU utilisation #133966

Open
Wendelstein7 opened this issue Dec 24, 2024 · 1 comment
Open

Proxmox VE integration: (very) high CPU utilisation #133966

Wendelstein7 opened this issue Dec 24, 2024 · 1 comment

Comments

@Wendelstein7
Copy link

Wendelstein7 commented Dec 24, 2024

The problem

Hi all! I am experiencing an unreasonably high CPU usage when using the Proxmox VE integration.

I am running a decently large Home Assistant setup featuring 120+ devices and 800+ entities. I am running natively (HA OS) on an Intel NUC. Over the past month, CPU utilisation has been stable between 1% and 2% utilisation.

Whenever I enable the Proxmox VE integration, my HA system's CPU utilisation rises to be stable between 3% and 4%. While not extreme by itself, I find it very weird that one integration (one of many) is capable of doubling the load on my HA system, also using a little over two watts extra in comparison to the exact same system but with the Proxmox VE configuration disabled.

To isolate the issue, I had Home Assistant run without Proxmox VE for an entire day and then ran it with it enabled for another day. In the CPU utilisation graph you can see very clearly where I added the Proxmox VE in my configuration.yaml and where I commented it out again (at the red arrows):

image

Should it be useful, I have attached the configuration I am using. Usually, around half of the given vm's and container's are online and the other half are not. I am not finding any log messages from proxmox or other signs of bad behaviour.

How come that one integration of the many, many I have can double the system load? I think this is probably a performance issue bug in the intergration somewhere and that is why I am making this issue report. Hope it helps, thanks!

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

proxmoxve

Link to integration documentation on our website

https://www.home-assistant.io/integrations/proxmoxve/

Diagnostics information

No response

Example YAML snippet

proxmoxve:
   - host: 10.0.0.<redacted>
     username: <redacted>@pve
     password: <redacted>
     verify_ssl: false
     nodes:
       - node: proxmox
         vms:
           - 100
           - 101
           - 102
         containers:
           - 103
           - 104
           - 105
           - 106
           - 107

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @jhollowe, @Corbeno, mind taking a look at this issue as it has been labeled with an integration (proxmoxve) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of proxmoxve can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign proxmoxve Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


proxmoxve documentation
proxmoxve source
(message by IssueLinks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant