Cannes: How Dropbox ML saves $1.7M a year on document preview pre-warming
Dropbox's Riviera system pre-warmed previews for all eligible files, but a significant portion of that pre-generated content was never viewed, generating considerable and unnecessary CPU and storage costs at petabyte scale.
Cannes replaced an estimated $1.7 million in annual pre-warm costs with $9,000 in ML infrastructure per year after being deployed to almost all Dropbox traffic, with no observed degradation to preview latency.
Frequently asked questions
What did this team achieve with this AI workflow?
Cannes replaced an estimated $1.7 million in annual pre-warm costs with $9,000 in ML infrastructure per year after being deployed to almost all Dropbox traffic, with no observed degradation to preview latency.
What tools did this team use?
Riviera, Suggest Backend, User Profile Service, Predict Service, Stormcrow, Grafana, Superset, RocksDB, Hive.
What results were reported?
Annual pre-warm cost replaced: $1.7 million; ML infrastructure cost per year: $9,000; Offline prediction accuracy: >70%; Pre-warm requests rejected by model: about 40% (source-reported, not independently verified).
How is this back office ops AI workflow structured?
File enters pre-warm path → Retrieve live activity signals → Encode signals and predict usage → Pre-warm routing decision → Log request for monitoring.