Upstash
Sandbox DAX

Last benchmarked October 16

Want the full logs for this run?Sign up free →

7/7 phases
✓ Prepare✓ Cache Clear✓ Bun Download✓ Bun Unpack✓ Clone✓ Install✓ Typecheck

Environment

Sandbox hardware and software context — use this to tell whether a provider is faster because of more CPUs/memory, not a faster disk or network.

Logical CPUs
48
Memory
185.3 GB
Architecture
aarch64
Kernel
Linux 7.0.0-1011-aws
Bun Version
1.3.14
Node Version
v25.9.0
Commit
08fb473

Estimated Cost

Median workload time x published rates at the 8 vCPU / 16 GiB sandbox spec. Excludes sandbox create/destroy time. This provider bills CPU on active usage, so the wall-clock figure shown is an upper bound.

Cost / Workload
$0.0058
Rate @ 8 vCPU / 16 GiB
$0.4000/hr
Billing Model
Active CPU
1,000 Workloads / Month
$5.77

Large box (8 vCPU / 16 GB): $0.40/active-CPU-hour — assumes 100% CPU utilization for the whole build. Source · Compare all providers

Disk Usage

Total disk usage (du -sx) captured after each phase — a proxy for disk I/O and storage cost. Some providers report 0 here if their sandbox filesystem doesn't support usable disk-usage reporting.

After Clone
334.1 MB
Repo size (source only)
After Install
0.0 MB
— from bun install
After Typecheck
0.0 MB
+— from typecheck

Total Duration Over Time

Prepare Over Time

Bun Download Over Time

Bun Unpack Over Time

Clone Over Time

Install Over Time

Typecheck Over Time

Raw Iterations

Each iteration runs the full clone + install + typecheck cycle from a fresh sandbox.

#PhasesTotalPrepareBun DLBun UnpackCloneInstallTypecheckError
17/751.94s3.91s0.28s0.62s2.49s9.97s25.02s—
PartnersGoogle Cloud Run