Throttled Live Dashboard
Summary
Reduce the calculation cost of a frequently updating report by throttling the narrowest part of the publish/receive path.
Files Used in This Example
Prerequisites
- A live workflow whose update rate and calculation cost have been observed.
- A defined freshness interval acceptable to dashboard users.
Step 1: Identify the expensive update layer
Separate source recalculation, publishing, subscription delivery, retrieval, and downstream dashboard calculation before changing a throttle.
Step 2: Throttle a publish with a blocked formula
Block the publish during ordinary recalculation and use a scheduled recalculation cell to release it.
Step 3: Use a numeric per-formula throttle when simpler
A numeric block value limits the publish frequency. The maintained recipe uses a negative interval when automatic recalculation at the end of the interval is unnecessary.
Step 4: Throttle receiving independently
A refresh can be driven by a slower trigger when consumers need data less often than it is published.
Result
The dashboard updates at the selected cadence while the source can continue changing more frequently.
What’s Happening
What’s happening here?
Publish throttles reduce outbound work; refresh or RTD throttles reduce inbound work. They solve different bottlenecks, so measure before stacking them.