Investigate CPU, memory and account limits
Use Resource Usage to connect slow periods with resource pressure.
Where Tools → Metrics → Resource Usage
Before you start
- Record when the slowdown occurred and which URL or action was affected.
- An account limit and actual consumption are different numbers.
Steps
-
1
Open Resource Usage and read the Dashboard summary. No issues in the past 24 hours describes that report window, not a guarantee of perfect performance.
-
2
Compare CPU, memory, disk I/O and process-related metrics when provided. A storage-space problem belongs in Disk Usage; an I/O limit concerns the rate of disk work.
-
3
Use Snapshot to inspect available records around the incident. A snapshot may not exist for every period, especially on a new account.
-
4
Share the relevant timeframe and measurements with support or your developer. Optimise the workload or address abnormal traffic before assuming a plan upgrade is the only answer.
-
5
Open Current usage or Details for the available usage and limit information. Check the displayed timeframe and units.
Dashboard, Current usage and Snapshot provide different views of resource pressure.
Check it worked
- Check a representative request after the fix and compare the same metrics.
- Do not conclude a brief spike caused the problem unless its timing matches the incident.