QUE SIGNIFICA CU(S) Y DURATION(S) en la app capacity metrics?

[agigutier]

Hola, 

tengo la siguiente duda: 
Que significa el dato: CU(S) y duration(s). por ejemplo:

Tengo estos datos, me dice que mi item en un día tardó 390,66 segundos, equivalente a 10 horas. Pero como es posible que haya tardado tanto? alguien me puede explicar?

[lbendlin · Accepted solution]

CUs (consumption units) are like a debt that you have to pay back.  Your capacity only has a limited number of CUs available for each 30 second timeslot.  Let's say you have 7680 CUs per slot, and your refresh had a cost of 100000 CUs. That means it will take 13 -ish 30 second timeslots to pay back that debt, but ONLY if there's nothing else happening on the capacity during that time. In the real world it will take much longer to repay the debt.

Look at the overage and burndown charts.

[Anonymous · Accepted solution]

Hi @agigutier ,
Based on the screenshot you provided, I checked the relevant  documents, CU generally refers to "Capacity Unit" and DURATION refers to the duration of an operation or query in seconds. 

The duration in the screenshot is 390.66, this data is given in seconds. To convert seconds to hours, you must divide the number of seconds by 3600 (since an hour has 3600 seconds). For example:

390.66 seconds / 3600 seconds per hour ≈ 0.1085 hours, which is approximately 6.51 minutes.

For more explanations and details on the terminology used in the capacity metrics app, you can refer to these official documents

Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn
Understand the metrics app storage page - Microsoft Fabric | Microsoft Learn
Understand the metrics app timepoint page - Microsoft Fabric | Microsoft Learn

Best regards

Albert He

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[lbendlin · Accepted solution]

CUs (consumption units) are like a debt that you have to pay back.  Your capacity only has a limited number of CUs available for each 30 second timeslot.  Let's say you have 7680 CUs per slot, and your refresh had a cost of 100000 CUs. That means it will take 13 -ish 30 second timeslots to pay back that debt, but ONLY if there's nothing else happening on the capacity during that time. In the real world it will take much longer to repay the debt.

Look at the overage and burndown charts.