harikrishna-patnala commented on issue #9555: URL: https://github.com/apache/cloudstack/issues/9555#issuecomment-2306543585
@rajujith I'm keeping the notes below based on our discussion privately. If you agree for this, we can close the issue. The "Limit" value is not related to the dynamic scaling or hot add feature. It is a setting for memory on a VM allows you to specify the maximum amount of memory that the VM can use, regardless of the amount of memory that has been allocated to the VM. If the utilization crosses the limit, then it will be swapped with disk. The maximum value which anyone can dynamically scale the VM is 16times of the memory when the VM is started. This is given from the VMware documentation. https://knowledge.broadcom.com/external/article/343190/cannot-hot-add-more-than-3gb-to-linux-64.html So setting limit value will not have any effect on the hot add limit. For CS to provide a way to configure this limit I think it will degrade the VMs performance later at some point. If multiple VMs on the same host are configured with "Unlimited" memory limits and high memory allocations, this can lead to resource contention. If the host does not have enough physical memory to satisfy the needs of all VMs, some VMs might experience performance degradation or may need to swap memory to disk. -- 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]
