> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/power-monitor/performance.md).

# Performance

Overview of the Performance module: average execution time, model performance assessment, model cleanup and Lakehouse and Warehouse diagnosis.

The **Performance** module gathers the Power Monitor screens that answer the question "why is it slow, heavy or expensive, and what do I optimize first?". It sits right after **Monitoring** in the side menu and brings together analyses that used to be scattered: the deviation in the execution time of models and Fabric items, the performance assessment of a semantic model, the cleanup of unused objects and the diagnosis of Lakehouse and Warehouse queries.

**How to access:** side menu **Performance**. All screens are available to every user profile and respect each person's **workspace scope**. Actions that change configuration (turning on tracking for an item, requesting a performance assessment) are exclusive to **Administrators**, and the corresponding button is hidden or disabled for the other profiles.

## The module screens

| Screen                                                                              | What it answers                                                                                                                           |
| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| [Average Execution Time](/en/power-monitor/performance/tempo-medio-de-execucao.md)  | Which semantic models, pipelines, Copy Jobs, Dataflows and Notebooks took longer than their historical average time, with an e-mail alert |
| [Performance Assessment](/en/power-monitor/performance/avaliacao-de-performance.md) | On-demand report of a semantic model: VertiPaq storage, Capacity Units consumption and optimization recommendations (Beta)                |
| [Model Cleanup](/en/power-monitor/performance/limpeza-de-modelo.md)                 | Tables, columns and measures that no report, relationship or measure uses and that can be removed                                         |
| [Lakehouse and Warehouse](/en/power-monitor/performance/lakehouse-e-warehouse.md)   | Diagnosis of the T-SQL queries and Capacity Units consumption of a Warehouse or of a Lakehouse SQL analytics endpoint                     |

{% hint style="info" %}
These screens appear here to make navigation easier, but they keep using the same data and the same rules as before. The old addresses keep working and open the screen in its new menu position.
{% endhint %}

## How the screens complement each other

{% stepper %}
{% step %}

### Average Execution Time

Find out **which items** started taking longer than normal.
{% endstep %}

{% step %}

### Performance Assessment

Open the model and see **why** it is slow or expensive, with prioritized recommendations.
{% endstep %}

{% step %}

### Model Cleanup

Reduce size and complexity by removing what nobody uses.
{% endstep %}

{% step %}

### Lakehouse and Warehouse

For storage items, investigate the T-SQL queries that weigh the most.
{% endstep %}
{% endstepper %}

## Related pages

* [Monitoring](/en/power-monitor/monitoramento.md): capacity consumption, data refresh and alerts
* [Data Quality](/en/power-monitor/qualidade-de-dados.md): Best Practices Score, AI Score and Environment Inventory
* [Efficiency Dashboard](/en/power-monitor/dashboards/dashboard-de-eficiencia.md): dead artifacts, ghost refreshes and cost per item


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.powermonitor.com.br/en/power-monitor/performance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.