weizhouapache commented on issue #12908: URL: https://github.com/apache/cloudstack/issues/12908#issuecomment-4147760533
@bernardodemarco proposal looks good overall. If I understand correctly, this means setting `maxMemory` for VMs with dynamic scaling enabled, right? I am wondering whether using global configurations is the best approach. In most cases, users tend to scale CPU/memory relative to the current VM size rather than relying on a fixed global limit. For example: - Relative scaling (e.g., doubling): 2GB → 4GB, 4GB → 8GB, 8GB → 16GB - Fixed increment scaling: 2GB → 4GB, 4GB → 6GB, 8GB → 10GB Would it make more sense to support scaling policies based on the current allocation instead of a global maximum? The global maximum can remain -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
