-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Tier settings not working #13
Comments
THank you to point me out to that, I will try to fix latest 2 issues togheter in my next free time slot, if someone wanna contribute in the meanwhile it will be appreciated! |
Hopefully fixed with this commit |
I don't think it's working, I set up a tier for a LXC to have at least 1024MB memory, but upon restarting the script it decreases to minimum set in the Default section - 512MB The Tier section is after the Default one in the yaml config file |
Thank you to note this, I will keep u posted here! |
Thanks! I am also having issues with two other things:
|
warm welcome :)) |
I agree with pear, I tested this yesterday and have this same issues. |
Should be fixed by using this approach(a62c82a). On my Proxmox node is working as expected also respect minimum ram settings. |
I don't think this fixed it :| Example: lxc_autoscale.json TIER_plex: cpu_upper_threshold: 80
2025-01-18 07:51:32 - INFO - Container 101: CPU usage: 0.0%, Memory usage: 30.12MB (97.65% free of 1280MB total), Initial cores: 1, Initial memory: 1280MB So the memory decrease appear to be working, however it ignores min_cores for the tier =========================================================================== TIER_emby:
2025-01-18 07:51:32 - INFO - Container 102: CPU usage: 68.5%, Memory usage: 22.98MB (99.67% free of 6912MB total), Initial cores: 6, Initial memory: 6912MB ======================================================================== TIER_jellyfin:
2025-01-18 08:13:59 - INFO - Container 115: CPU usage: 40.0%, Memory usage: 52.88MB (98.71% free of 4096MB total), Initial cores: 5, Initial memory: 4096MB So here it decreased CPU cores count, but didn't even touch the memory. BTW, are the CPU stats in PVE console the same as those the scripts is seeing? In shell i see that CPU usage for CT115 is less than 2% : Whereas in the scripts log file: 2025-01-18 08:23:00 - INFO - Container 115: CPU usage: 40.0%, Memory usage: 46.91MB (98.85% free of 4096MB total), Initial cores: 5, Initial memory: 4096MB |
Describe the bug
Even though I use sample tier settings, all lxc containers are scaled to default settings. When debugging the settings for each container it came out that they were default (only added print in
scaling_manager.py
afterconfig = DEFAULTS.get(f"TIER_{ctid}", DEFAULTS)
).To Reproduce
Steps to reproduce the behavior:
Additional context
Python 3.11.2
Kernel Version: Linux 6.8.12-4-pve (2024-11-06T15:04Z)
Manager Version: pve-manager/8.2.8/a577cfa684c7476d
logs.txt
lxc_autoscale.txt
The text was updated successfully, but these errors were encountered: