Resource Usage and Choosing the Right Plan for WordPress
Read the live bars and the history graphs, understand the upgrade advice and change your workspace size.
A WordPress site uses part of the Cloud Workspace it runs on. The Resource Usage views show how much, now and over time, so you can tell whether the site fits.
Live usage
On the app's Overview tab, the CPU and memory card shows live bars for CPU, memory and storage. CPU is shown against the cores you have, for example "2% of 400% (4 cores)": a full core is 100%.
History
The Resource usage link in that card opens a page with CPU and memory graphs for 24 hours, 7 days, 30 days or 90 days. On each graph:
- the filled area is the average,
- the thin line is the peak,
- the dashed red line is your plan's limit.
Hover over a point to see the exact time and values. FlyNode keeps minute-by-minute detail for about a week and daily summaries for longer.
The upgrade advice
When the site spends most of its time close to the limit, a banner appears with a suggested next Cloud Workspace size. It warns when usage is at 80% or more for most of the period, and raises the warning when it is at 92% or more for half of it. The suggestion is the cheapest size that adds the memory or CPU you are short of. Short spikes (a backup, an import) do not trigger it.
Changing the size
Change the workspace size from Subscription in the left menu. The rules are the same for every Cloud Workspace:
- Upgrade: you pay the new size for the days left in the current period, minus credit for the unused days of the old size. Your billing date does not move.
- Downgrade: free, and your billing date does not move.
The dashboard shows the exact amount before you confirm. The database and cache memory of your WordPress sites follow the new size.
If the site is slow but usage looks low
Slowness is not always about size. Check, in this order: plugins that are out of date or heavy (the Security overview lists them), a large uploads folder, and whether the country block or Under Attack mode is on (both turn the page cache off).
Still stuck?
Open a support ticket from your dashboard and include the container name.