Modal adjusts Sandbox resource allocation strategy
The story so far
Modal has changed its Sandbox resource allocation strategy from fixed reservation to on-demand burst to accommodate burst workloads. The platform claims that in typical usage, the Sandbox only peaks during dependency installation, testing, or building, while the fixed resource reservation model forces users to reserve resources for peaks and pay continuously. The new on-demand burst model only acquires CPU and memory resources when needed, and users pay based on actual usage, with average costs potentially 58% lower than the fixed reservation model.
AI-written from the reports · Updated 2 days ago
Coverage timeline
Follow the coverage to see every side of the story.
- Modal BlogModal's Sandbox resource allocation: on-demand burst rather than reserved
Modal's Sandbox only uses up to 6% of the peak CPU in typical usage, as it is idle during inference and only peaks when dependencies are installed, tested, or built. The current fixed resource reservation mode is not suitable for such bursty workloads, forcing users to reserve resources for peaks and pay continuously. Modal's Sandbox adopts an on-demand burst mode, acquiring CPU and memory resources only when needed, and users pay based on actual usage, with an average cost 58% lower than the fixed reservation mode.
Heat over time
- Now
- 3
- Peak
- 813 Nov, 10:00
- 24h change
- -49%
Hover or tap the chart to see each hour; use the arrow keys on a keyboard.