
The [Resource Consumption](dashboard:XbtxCLG) dashboard provides a comprehensive analysis of resource consumption, allowing you to identify which projects or users are consuming resources, and on which infrastructure.
This dashboard features 4 distinct tabs, each offering a different perspective on resource usage:

## General Analysis

![general_analysis.png](KuWBEL7hm0IF)

 **Monitor your resource consumption.** 
- Distribution of resource consumption over days/hours: Analyze resource consumption patterns throughout the day and week. Schedule jobs during off-peak hours when the platform is under-utilized.
- Distribution of resource consumption over each execution infrastructure: make sure users leverage SQL engines as much as possible for compatible recipes, as they often provide more efficient processing.
- Most frequent job: review recurring jobs to ensure they are triggering as intended and not unnecessarily, optimizing scheduling.

## Instant Usage Monitoring

![instant_usage.png](ieoeOQLk1X6T)

 **Perform capacity planning.** 
 To effectively perform capacity planning and understand peak resource demands, use the dashboard to investigate which projects, users, or recipes generated CPU and memory peaks.
 For each resource (memory & CPU) : 
- on the left side, there is a chart showing the overall usage of the platform(s)
- on the right side, a chart displays the minutes with the highest resource usage. Clicking on this chart will display a more detailed view.
You can filter on the left on a date, execution location, project key, and user id.

## Cumulative resource usage over time

![cumulative_resource_usage.png](mKovTDolgHaq)

 **Analyze cumulative resource consumption over time to identify jobs and projects that are resource-intensive, allowing for optimization to diminish CO2 impact and reduce financial costs.** 
For each project, you will find its cumulative memory and CPU usage.

## SQL Details

![sql_details.png](igk2EdX8bhaw)

 **Analyze the SQL execution time for all your projects.** 
 It displays the daily SQL execution time per project, along with the distribution of executions across your available SQL connections.



