Namespace vs SFCompute

Sandbox Benchmark Comparison · Updated November 20, 2026

SFCompute was faster in the only shared sandbox benchmark.

Head to head

  • Total workload time · lower is better
    SFCompute faster1.34x
    Namespace
    53.40s
    SFCompute
    39.91s

DAX

November 20, 2026

Namespace

100% success
Median
53.40s

SFCompute

100% success
Median
39.91s

Median total workload time over time

5 runs · September 16, 2026 to November 20, 2026
NamespaceSFCompute

Cost per DAX run

Namespace

Per-minute unit minutes
$0.012per run
53.40s median at $0.7200/hr

8 vCPU/16 GB shape = 8 unit-min/min at the pay-as-you-go rate of $0.0015/unit-min. Team/Business plans include prepaid minutes at an effective $0.001/unit-min ($0.48/hr). Bills in 1-minute minimums with 15-second rounding.

Source pricing page

SFCompute

Per GiB-hour (parkable)
$0.0081per run
39.91s median at $0.7315/hr

Rollout sandboxes at $0.04572/GiB-hr while active (16 GiB); parked/idle drops to ~$0.000139/GiB-hr. Interactive cpu-8 node is $0.4824/hr with a 15-min minimum.

Source pricing page
Compare sandbox costs across all providers
Work at Namespace or SFCompute? 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 was faster in the only shared sandbox benchmark. In DAX (November 20, 2026), SFCompute had a median total workload time of 39.91s versus 53.40s for Namespace, 1.34x faster.

Both providers have results in 1 sandbox benchmark: DAX. It has a speed verdict.

Success rates in the latest runs: DAX: Namespace 100%, SFCompute 100%.

DAX results are from November 20, 2026.