> For the complete documentation index, see [llms.txt](https://mango-5m.gitbook.io/mango5m-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mango-5m.gitbook.io/mango5m-docs/resources/mango-admin/features/performance.md).

# Performance

Frame time, ping, database, entities and one honest health score.

| Measure        | What it is                                    |
| -------------- | --------------------------------------------- |
| **Frame time** | Server tick, p50 and p99, against your budget |
| **Ping**       | Across connected players, average and p95     |
| **Database**   | How long a `SELECT 1` round trip takes        |
| **Entities**   | Vehicles, peds and objects in the world       |
| **Resources**  | How many are started, and how many fell over  |
| **Uptime**     | How long the server has been up               |

Charts cover the last hour, 24 hours or 72 hours. Samples are taken once a minute and written to disk every five, so the history survives a restart.

## The health score

One number out of 100, from the parts above weighted in `Config.Health`. Two things make it honest:

* **A part the server cannot measure is left out** and the rest rescaled — no database means the score is out of what can actually be seen, not penalised for a thing that does not exist.
* **Only a resource that WAS running and now is not** counts as down. A server carries dozens it never intended to start; counting those pinned the score at zero permanently, which made stopping something appear to change nothing. One you stopped yourself from the panel is not held against it either.

{% hint style="info" %}
This page polls once a second while it is open, and stops the moment it is not. Everything else in the panel runs on a five-second tick that carries only what changed.
{% endhint %}