๐ฆ๐ผ ๐๐ต๐ฎ๐ ๐ถ๐ ๐ฆ๐๐ฟ๐ด๐ฒ ๐ฃ๐ฟ๐ผ๐๐ฒ๐ฐ๐๐ถ๐ผ๐ป?
Essentially, surge protection prevents background jobs taking up too much of your capacity allowance.
A background job is typically a scheduled job, like a scheduled pipeline run, or a scheduled semantic model refresh. As opposed to interactive queries - these normally involve a user clicking on buttons in the UI. Both interactive and background job capacity usage are reported in the Capacity Metrics App. ๐๐ผ๐ ๐ฑ๐ผ๐ฒ๐ ๐ถ๐ ๐๐ผ๐ฟ๐ธ?
- You define a threshold ("Background Rejection Threshold"), for example 75%. This means that when background jobs are consuming >75% of your capacity, they will begin to be rejected.
- You define a second Recovery threshold, which could be 50%. When the Background Recovery threshold is reached, surge protection stops rejecting operations. The capacity then resumes accepting new background operations.
๐๐บ๐ฝ๐น๐ฒ๐บ๐ฒ๐ป๐๐ฎ๐๐ถ๐ผ๐ป ๐ป๐ผ๐๐ฒ๐:
- You configure surge protection for each capacity.
- Before you set the two thresholds, check your capacityโs 24 hours background %. Avoid setting the value too low too quickly to prevent impacting users.
Let me know if you'll be turning on this feature! Please note: this is still a preview feature, so you'll need to bear that in mind.