Compare load and symptoms
Record the exact symptom and time before reading CPU or memory. One busy sample cannot identify a process or justify resizing.
Note onset and time zone, including nearby deployments or scheduled jobs. A brief CPU peak during a backup differs from sustained pressure, and used RAM may include cache; neither reading alone proves an application shortage.
Use only monitoring that your account actually exposes. Virtualizor documents end-user monitoring, but the service agreement and panel permissions determine whether you can view it. For VM Start with Managed OS, the customer retains root access; coordinate OS tuning with Novasean and keep application diagnosis with its owner.
Record the readings your account actually shows
If authorised Virtualizor monitoring is available, select the correct VPS and record the CPU and memory values the account actually displays, with the time and time zone of each reading. Repeat readings during the symptom and, if practical, during a quieter period. Do not infer historical peaks or a sampling interval from a current snapshot. If your installed panel provides an authorised history view, label it as such and note its period and scale; otherwise ask the operator whether retained guest or platform metrics exist. A high CPU reading says the guest was busy at that moment; it does not identify the process. A low apparent free-memory figure likewise needs guest evidence before it can be attributed to pressure.
If the panel shows no metrics or the readings appear stale, do not invent a trend. Send support the service identifier, the observed values or absence of a reading, their times and the affected URLs or processes.
A panel snapshot taken after a spike cannot establish its peak or duration. Ask for retained metrics only if the operator has them.
Connect resource evidence to the workload
Ask the application owner whether requests, batch jobs, deploys or database work changed at the same time. An authorised operator can compare guest process and memory-pressure evidence with the time-stamped panel readings, if available, and look for an out-of-memory event. Keep customer-facing reports at the symptom and aggregate level; avoid pasting secret-bearing process arguments or private logs into a ticket. If the website is slow but CPU and memory are normal, investigate network, storage and application timings instead of requesting a larger VM by default.
The disk-capacity guide covers a full filesystem. Storage exhaustion can coexist with CPU pressure, but requires its own measurement and recovery path.
Illustrative comparison: CPU reaches a brief peak during a scheduled job, but request latency stays normal. Record both; a resize is not supported by that sample alone.
Request a bounded change and verify
Agree whether the next action is an application correction, scheduled workload change, operator investigation or capacity review. If the evidence supports a capacity review, use the VPS right-sizing worksheet to record an initial choice, uncertainty and review triggers. For a managed service, ask the named operator before a privileged restart, package change or VM sizing decision. Preserve a known-good deployment and an agreed recovery route. After the change, compare the same symptom and time-aligned metrics, not merely a lower single reading. If the service worsens, return to the previous application version or ask the operator to execute the documented recovery decision.
Frequently asked questions
Does 100% CPU mean my VPS is broken? It means the measured CPU was busy over that sample; duration and service impact determine urgency.
Can I fix low free memory by rebooting? A reboot may erase useful evidence and only reset a recurring problem. Capture the symptom and involve the responsible operator before taking that step.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.