Allocated params
473Mbrowser tab, Memory64 buildhistoricalMemory64 Browser Behemoth Allocation
The Memory64 work is a useful public artifact because it has a crisp blocker, a measurable unlock, and a compatibility lesson: browsers can train larger local models, but feature detection matters.
Headline Numbers
Evidence class applies to each value: measured = retained evaluation or runtime result; historical = recorded result not freshly reproduced; derived = calculated or decided from records; observed = current artifact state; not-measured = an explicit evidence gap.
Allocation time
3.7smeasured Behemoth allocationhistoricalTrain step
82.2ssingle sanity step after allocationhistoricalCompetitive Context
| System | Metric | Score | Size / Class | Comparable? | Readout |
|---|---|---|---|---|---|
| posttrainllm Memory64 build | browser allocation ceiling | 473M params | >4GB heap path | Direct | Shows the browser can allocate beyond the old wasm32 limit on supported runtimes. |
| posttrainllm wasm32 build | browser allocation ceiling | OOM around 4GB | 32-bit heap path | Direct | Baseline failure mode that Memory64 fixes. |
Direct rows share this artifact's eval setup. Directional rows are useful market context but should not be read as leaderboard claims.
Memory ceiling
| Build | Outcome | Why |
|---|---|---|
| WASM32 | OOM around 4GB heap | 32-bit pointer ceiling |
| WASM Memory64 | 473M params allocated | 64-bit memory address path |
Release Blockers
Browser support variability
Memory64 descriptor spelling and support differ across browser versions.
Unblock: Keep runtime feature detection and clear fallback copy.