mirror of
https://github.com/cvk98/Proxmox-load-balancer.git
synced 2026-04-25 04:25:50 +03:00
[GH-ISSUE #22] CPU Balancing #13
Labels
No labels
documentation
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxmox-load-balancer#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cvk98 on GitHub (Mar 4, 2024).
Original GitHub issue: https://github.com/cvk98/Proxmox-load-balancer/issues/22
@cvk98 However, I have noticed that the CPU load is also an issue in my cluster size, which unfortunately must not be forgotten. Possibly with average values of the last 24 hours. Would be cool if you still want to think about it and integrate it. If you need information or similar, please ask me.
Originally posted by @c-sakel in https://github.com/cvk98/Proxmox-load-balancer/issues/7#issuecomment-1975990359
@cvk98 commented on GitHub (Mar 4, 2024):
Regarding CPU balancing:
@c-sakel commented on GitHub (Mar 4, 2024):
I am aware that it is very difficult to balance CPU and memory, but in my case it is unfortunately not possible to check in advance which machine will use a lot of CPU, as the machines are created and managed dynamically. I think this could be a use case for several people. Balancing with CPU/memory would definitely be a great solution.
@cvk98 commented on GitHub (Mar 4, 2024):
I'm not taking this job. Now I don't have as much free time as I used to, unfortunately.
@c-sakel commented on GitHub (Mar 4, 2024):
That is not a problem. I just wanted to suggest it as feedback on the software and possibly present my idea in the great project. Thanks for your review!