Reitse Eskens on 26 Mar 2024 15:33:35
Fabric offers the option to temporarily burst the capacity to max three times the power that is associated with the SKU.
This works fine, but at some point the overage needs to be burnt down, leading to throttling or even rejection.
I'd like to have the option to limit bursting or even turn it off to prevent the throttling and rejection all together. This would have an impact on the duration of interactive and/or background processes. Overall, I think it will lead to a better user experience when it's just clear that the chosen SKU is insufficient for that point in time and should be upgraded to a higher one. This is an easier discussion with a client than having to explain why there were error messages about the capacity 'not working'.
Santhosh Kumar Ravindran (administrator)
Have added it to our backlog and this ask is under internal review. Stay tuned for updates. Thank you!
- Comments (3)
RE: Limit bursting
This is a must and also there is a big in the bursting when pausing a capacity. When capacity is paused for that second consumption shows as in million of CUs
RE: Limit bursting
Thank you sharing this. For spark workloads I have included this to my list for the upcoming semester to make the burst factor configurable.
RE: Limit bursting
A configurable parameter for bursting would be nice. For example x times bursting.You're alone on the capacity because you're the sole dev? Set it to 10 and enjoy the speed!You have to share a capacity globally and you don't want to borrow capacity from other time zones? Set it to 1 (which would mean no bursting).