Hi @Anonymous ,
Yes as you said, Interactive CUs are mainly used during user interaction with reports. When a user queries or interacts with a report powered by the DirectLake schema, the system uses the interactive CUs to process these requests in real time.
Background CUs may not be mentioned directly in the context of DirectLake operations, but it is important to understand that background CUs are typically used by operations that run in the background without immediate user interaction. This includes data refresh operations, application model changes, or other maintenance tasks.
DirectLake mode primarily affects interactive CUs because it enhances the user interaction experience by providing faster data retrieval and analysis capabilities. However, keeping incremental lake files or parquet files up-to-date (e.g., through database mirroring or scheduled refreshes) can consume background CUs, depending on the specific operations required to keep data up-to-date.
While the DirectLake schema itself focuses on optimising interactive analysis of large datasets, any background operations required to maintain data readiness (such as updating incremental tables or managing parquet files) will still follow the general principles of CU usage in the fabric.
Unfortunately, there is no direct reference to database mirroring in the DirectLake context in the provided documentation. However, it is reasonable to assume that operations related to data maintenance or updates running in the background will use the background CUs in accordance with the standard operations for fabric resources.
For more insight into DirectLake the following documentation may be helpful:
Learn about Direct Lake in Power BI and Microsoft Fabric - Power BI | Microsoft Learn
Learn how to analyze query processing for Direct Lake datasets - Power BI | Microsoft Learn
Best Regards,
Ada Wang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
