Author
system Submitted
Jun 14, 2026 6:59am Summary
KB drift-audit reconciliation 2026-06-14: corrected to match dev (report deliverables). Admin: Performance Monitor
The Performance Monitor at Admin → Performance shows how fast your community is serving requests over the last 24 hours.
What it shows
- Slowest endpoints. The top 10 routes by response time in the last 24 hours.
- Slow requests. A count of requests that took longer than 500 ms.
- Error rate. The share of requests flagged as slow, as a percentage.
- Recent slow requests. A table of the latest slow requests with the URL, method, duration, memory used, and the member who triggered it.
Interpreting the data
- A spike in slow requests usually means a traffic surge or a heavy page. Check the slowest-endpoints list to see which route is responsible.
- A single member appearing repeatedly in the recent-slow table can point to an expensive search or export they are running.
Use this page to spot a regression early and decide where to dig in next.
## Admin: Performance Monitor The Performance Monitor at **Admin → Performance** shows how fast your community is serving requests over the last 24 hours. ### What it shows - **Slowest endpoints.** The top 10 routes by response time in the last 24 hours. - **Slow requests.** A count of requests that took longer than 500 ms. - **Error rate.** The share of requests flagged as slow, as a percentage. - **Recent slow requests.** A table of the latest slow requests with the URL, method, duration, memory used, and the member who triggered it. ### Interpreting the data - A spike in slow requests usually means a traffic surge or a heavy page. Check the slowest-endpoints list to see which route is responsible. - A single member appearing repeatedly in the recent-slow table can point to an expensive search or export they are running. Use this page to spot a regression early and decide where to dig in next.
