Understanding Performance dashboard vs. capacity metric dashboard

Hello Anonymous 

could you please confirm if Sql database is the only workload utilising the F16?

SQL Database uses only a portion of Fabric’s total capacity (1 Fabric CU = 0.383 SQL vCores). A Fabric F64 SKU (64 CUs) provides ~24.5 SQL vCores, leaving ~39.5 CUs for other workloads like Power BI, Data Engineering, or KQL databases

Throttling occurs at the capacity level, not per workload. Even with low SQL CPU usage, concurrent workloads (e.g., Spark jobs, Power BI reports) can collectively exceed capacity limits

Most SQL operations are classified as interactive in Fabric and smoothed over 5-minute windows. Short, frequent queries or system tasks (e.g., metadata updates) can spike CU usage without significantly impacting SQL CPU

this is mainly for guidance. 

thanks