How do I plan a VPS CPU or RAM upgrade?
Increase resources when measurements show a relevant capacity constraint and the selected upgrade addresses it. Confirm whether the provider operation requires shutdown, restart or migration, then verify the new allocation inside the guest.
Instructions
1. Measure the actual bottleneck
Record busy-period application response, CPU demand, memory pressure, disk latency and any relevant quota. More RAM will not directly fix a blocked network path, and extra vCPUs may not help a single-threaded task.
2. Review the permitted service change
Confirm the new allocation, price, downtime, storage effect and any rollback or migration conditions with the available control or support. Do not assume every plan can be resized online. Coordinate a maintenance window if interruption is required.
3. Verify the guest after completion
Wait for the provider operation to reach its final state, then inspect Linux-visible capacity.
lscpu
free -hCompare visible processors and memory with the approved target. Recheck application behaviour and any service or container quotas that remain at their old limits.
Check the result
- Provider and guest allocation match the approved upgrade.
- The measured application constraint improves without unexplained service failures.
Troubleshooting
- The panel shows more RAM but Linux does not
- Check whether a restart or supported memory-online step is required for this image.
- The application still has its previous limit
- Its own heap, worker, service or container settings may need a separately reviewed adjustment.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.