Capacity management in Fabric

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
data-engineering, documentation

Research direction

Start by reviewing the two linked references on Fabric capacity smoothing, throttling, bursting, and workload management, then inspect the repository's existing drawings for the appropriate format and scope. Done means a clear visual explanation covers CU, capacity sizing, smoothing, workload calculations, and a ballpark estimation method.

Written by the indexing model from the issue text.

Description

Note request

What concept do you need more clarity on?
Capacity: CU, busting, smoothing, workload management, how to calculate a workload (e.g. one copy activity = 3 seconds -> 3000 ms, that correlates with XXXXCU times 4 CU in F4, etc). Maybe some ballpark capacity estimation

Any reference explaining that concept
https://learn.microsoft.com/en-us/fabric/data-warehouse/compute-capacity-smoothing-throttling
https://data-mozart.com/bursting-and-smoothing-yin-and-yang-of-the-fabric-capacity/

Have you checked the list of issues to see if there is a similar suggestion?

  • [ X ] Yes, I have checked
Dominant language
CSS
Stars
118
Forks
31
Avg merge
4d 13h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/fabricnotes

All issues in microsoft/fabricnotes

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.