Google Cloud Run vs Tensorlake

Sandbox Benchmark Comparison · Updated November 6, 2026

Google Cloud Run
Faster in
0of 1 benchmark
#30 of 31 in Sandbox Provider Rating
vs
Tensorlake
Faster in
0of 1 benchmark
#8 of 31 in Sandbox Provider Rating

Google Cloud Run and Tensorlake were roughly even in the only sandbox benchmark with a speed verdict.

Head to head

  • Burst TTITime to interactive · lower is better
    Roughly even
    Google Cloud Run
    1.62s
    Tensorlake
    1.55s
  • DAXTotal workload time · lower is better
    No verdict
    Google Cloud Run
    —
    Tensorlake
    78.16s

Burst TTI

November 6, 2026
Full leaderboard

Google Cloud Run

100% success
Median
1.62s
p95
2.52s
p99
2.65s
Google Cloud Run Burst TTI results

Tensorlake

100% success
Median
1.55s
p95
1.82s
p99
1.84s
Tensorlake Burst TTI results

Median time to interactive over time

26 runs · July 8, 2026 to November 6, 2026
Google Cloud RunTensorlake

DAX

Full leaderboard

Google Cloud Run

0% success · October 30, 2026

No measured time in this run.

Google Cloud Run DAX results

Tensorlake

100% success · October 23, 2026
Median
78.16s
Tensorlake DAX results
Work at Google Cloud Run or Tensorlake? 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 →Raw results on GitHub ↗

Frequently asked questions

Have another question? Email us.

Google Cloud Run and Tensorlake were roughly even in the only sandbox benchmark with a speed verdict. In Burst TTI (November 6, 2026), Google Cloud Run had a median time to interactive of 1.62s and Tensorlake 1.55s, which counts as roughly even.

PartnersTigris