Forum Discussion

db042190's avatar
db042190
Icon for Impactful Individual rankImpactful Individual
3 months ago
Solved

are multiple fabric capacities ever warranted

hi, after we saw how easily fabric is brought to its knees (right in the middle of a critical project by a fabric event handling experiment someone ran), we started wonderig if running multiple fabric capacities might be one way of mitigating the scenarion of one bad apple spoiling it for the rest.   are multiple capacities sometimes warranted?  at the moment our consultant recommended 3 ws's, dev, test and prod.  its been a while but my recollection of pbi is that you can have all 3 in one ws.

 

we did turn on fabric alerts.   we want to look into whether fabric has functionality where horsepower,, ie the peice of the compute pie, can be limited on a ws or user level.  do you think we'll hit a wall on that idea?   

2 Replies

  • The isolation unit in Fabric is the capacity, not the workspace.
    So putting prod on its own capacity and dev/test on another is the safe way to avoid one heavy workload slowing everything. And right now Fabric doesn’t offer per‑workspace or per‑user compute limits, only capacity level controls like metrics and alerts.

  • Hi db042190 

     

    It actually is possible to put workspace limits in terms of background capacity usage which can help you then balance your single capacity. Ideally it is recommended though to use different capacities for dev test and different capacities for prod. Here is the learn document on how to configure. Background limitations. https://learn.microsoft.com/en-us/fabric/enterprise/surge-protection#workspace-level-surge-protection