# Top Queries

Datasentinel collects incremental execution statistics for all queries every minute.

This makes it easy to identify the top-performing queries over a specific period and on specific metrics, such as those generating the most Disk Access, Temporary Disk I/O or taking the most Execution Time.

The dashboard comprises three parts:

* The upper graph provides a visual representation of the queries impact over time.
* The small intermediate graphs help correlate these statistics with [Cluster or System Metrics](https://docs.datasentinel.io/manual/features/key-features/cluster-and-system-metrics).\
  Refer to[ Metric  Correlation](https://docs.datasentinel.io/manual/features/tips-and-hints/metric-correlation) for more details.
* The lower part provides details on a query-by-query basis for all the execution statistics

This feature allows for in-depth analysis of top queries across various dimensions, including:

> * total time
> * calls
> * rows
> * shared blocks hit
> * shared blocks read
> * shared blocks dirtied
> * shared blocks written
> * temporary blocks read
> * temporary blocks written
> * read time
> * write time
> * local blocks hit
> * local blocks read
> * local blocks dirtied
> * local blocks written
> * WAL size (since Postgres 13).

{% hint style="info" %}
It also displays the run-time statistics globally, by call, or by second.
{% endhint %}

### Interactive Demo

{% @arcade/embed flowId="zqHL2iACv4c1wNcot6bV" url="<https://app.arcade.software/share/zqHL2iACv4c1wNcot6bV>" %}

> *The dedicated dashboard presents the information in a multi-dimensional manner, featuring Time selection, Time zooming, and Tag filtering options.*

**Datasentinel** lets you explore individual queries in depth, with access to historical metrics and execution plans, helping you proactively monitor performance and pinpoint database bottlenecks.

### Explore execution plans

{% content-ref url="../other-features/execution-plans" %}
[execution-plans](https://docs.datasentinel.io/manual/features/other-features/execution-plans)
{% endcontent-ref %}
