sfcompute vs Sprites

Sandbox Benchmark Comparison · Updated November 20, 2026

sfcompute and Sprites have no shared sandbox benchmark with a speed verdict.

Head to head

  • Time to interactive · lower is better
    No verdict
    sfcompute
    621ms
    Sprites
    31.60s20%
  • Total workload time · lower is better
    No verdict
    sfcompute
    39.91s
    Sprites
    —

Burst TTI

November 20, 2026

sfcompute

100% success
Median
621ms
p95
765ms
p99
766ms

Sprites

20% success
Median
31.60s
p95
62.41s
p99
62.41s

Median time to interactive over time

2 runs · November 6, 2026 to November 20, 2026
sfcomputeSprites

DAX

November 20, 2026

sfcompute

100% success
Median
39.91s

Sprites

0% success

No measured time in this run.

Work at sfcompute or Sprites? See where you stand every day, with full run logs, not just on benchmark Friday.Get stealth benchmarks

Methodology

  • One workload, every provider. The same script, payload, and model hit every provider, addressed the way its own API expects. Nobody gets a tuned or special path.
  • Repeated on a schedule. Every suite runs many iterations per provider, automated on a recurring schedule, so results reflect steady state rather than one lucky request.
  • Raw results published. Every run is committed as JSON to the public benchmarks repo, next to the code that produced it. Nothing is cherry-picked or held back.
  • How this comparison is built. Each benchmark compares the two providers' medians; results within 5% count as roughly even. A comparison is published when both providers have at least one successful run in the same benchmark from the last 30 days. A benchmark only gets a verdict when both providers completed at least 50% of its runs. If a provider’s latest run of a benchmark failed, its most recent successful run from that window is used instead.
Read the full methodology

Frequently asked questions

Have another question? Email us.

sfcompute and Sprites have no shared sandbox benchmark with a speed verdict.

Both providers have results in 2 sandbox benchmarks: Burst TTI and DAX. 0 of them have a speed verdict.

Success rates in the latest runs: Burst TTI: sfcompute 100%, Sprites 20%; DAX: sfcompute 100%, Sprites 0%. Burst TTI has no speed verdict because Sprites completed fewer than half of its runs; sfcompute's median time to interactive was 621ms. DAX has no speed verdict because Sprites completed fewer than half of its runs; sfcompute's median total workload time was 39.91s.

Burst TTI and DAX results are from November 20, 2026.