Service resource usage: see your RAM and CPU on Voroa
See how much memory and CPU each Voroa service uses against its plan limit on the service Overview, and get an early warning before it runs out of headroom.
Every Voroa service runs on a plan that gives it a fixed amount of memory (RAM) and CPU. The service Overview shows how much of each your service is actually using, so you can tell at a glance whether it has room to grow or is close to its limit.
Where to find it
Open a service and look at the Plan card, on either the Overview tab or the Compute page. Below your current plan you will see two thin bars:
- RAM — memory the service is using, shown against its plan allowance.
- CPU — how hard the service’s processor share is working.
Each bar is colour-coded so the state is obvious without reading the numbers:
- Blue — comfortable headroom.
- Amber — getting busy; worth keeping an eye on.
- Red — near the limit.
If a bar shows a dash (—) instead of a value, usage data has not been recorded for that service yet. Newly created services take a few minutes to report their first reading.
Seeing the last 48 hours
The bars show the reading taken a few minutes ago. The Compute page of a service also charts the last 48 hours, so you can see whether a service has been steady, is climbing, or spiked overnight.
Two things about those charts are worth knowing, because they are not what the numbers look like at first glance:
- If your service runs more than one copy, the chart shows the busiest copy, not the average across them. Adding copies will not pull the line down on its own.
- Memory is a reading taken every five minutes. CPU is the average across each five-minute interval, so a short spike inside one interval is smoothed into it and will not show as a peak.
Charts need a few readings before there is a trend to draw, so a service will show a short note instead of a chart until enough have arrived.
The 80% warning email
When a service crosses about 80% of its RAM or CPU allowance, Voroa sends the workspace a single “upgrade or optimize” email. Running that close to the limit can slow the service down or cause it to restart under load, so the email is an early heads-up — not an outage alert.
You will get the email once each time a metric climbs into the high range. It re-arms only after the service settles back down well below the limit, so a service hovering near the threshold will not email you repeatedly.
What to do about high usage
You have two options:
- Upgrade the plan. A larger plan gives the service more memory and CPU. Use the Upgrade button on the Plan card. Your service keeps running while the change applies.
- Optimize the service. Reduce what the service loads into memory, cache less aggressively, or fix a process that is using more CPU than it needs. Often a small change frees up plenty of headroom.
Either way, the goal is the same: keep the bars out of the red so your service stays fast and stable.