Can VPS CPU and memory changes take effect without a restart?
Online resource changes require support from the provider platform, virtual-machine configuration and guest operating system. A provider accepting a resize request does not guarantee that the guest has made the new resource available to applications.
Instructions
1. Confirm the supported change path
Ask whether the exact CPU or RAM change is online, requires guest onlining, or needs a full stop/start. Memory removal is a different operation from addition and can have stricter limitations.
2. Inspect resources visible and active in Linux
Use read-only views after the provider reports completion.
cat /sys/devices/system/cpu/online
lsmem
free -hThe CPU list shows online processors. lsmem reports memory blocks where supported, and free shows usable memory. A container may not expose the same hotplug interfaces.
3. Follow the image’s supported activation procedure
Do not write blindly to sysfs to force resources online or offline. Use the distribution and provider’s procedure for the exact change. If a restart is required, coordinate it and recheck service health afterward.
Check the result
- The guest’s online CPU and memory totals match the requested allocation.
- Applications can use the new capacity and remain healthy after any required restart.
Troubleshooting
- Resources are present but offline
- Review the guest OS hotplug policy and supported activation process.
- The provider cannot perform an online change
- Schedule the documented stop/start or migration procedure rather than repeatedly resubmitting the resize.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.