Hi @Strizzolo ,
To enforce CPU throughput limitations, Power BI evaluates the throughput from your Premium Gen2 capacity on an ongoing basis.
Power BI evaluates throughput every 30 seconds. It allows operations to complete, collects execution time on the shared pool physical node’s CPUs, and then for all operations on your capacity, aggregates them into 30-second CPU intervals and compares the results to what your purchased capacity is able to support.
Background operations such as dataset and stream refreshing or interactive operations such as querying and report loading can require significant CPU resources, which do not seem to be caused by track activities.
Many cases can cause high CPU usage or saturation，This can often be improved by optimizing the model.
Please optimize your data model in the way mentioned in this similar thread：
Optimizing-the-datasource-CPU-usage
Also ,when a dataset is consumed in short bursts of high frequency queries by multiple users (for example, in a training session), resulting in CPU saturation during each burst.
In some cases, Power BI administrators can request that dataset owners create a less volatile query workload by creating a dashboard (which queries periodically with any dataset refresh for cached tiles) instead of a report. This can help prevent spikes when the dashboard is loaded.
This solution may not always be possible for given business requirements, however it can be an effective way to avoid CPU saturation, without making changing to the dataset.
For more information，you can refer to：
Determining whether there is enough CPU
Suddenly receiving Balance your overloaded Power BI Premium capacity
Hope it helps,
Community Support Team _ Caitlyn
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
