Skip to content

docs(capacity): DriveRole::Cold is FROZEN storage, never the per-token streaming tier (#302 slice 0) - #2115

Merged
joelteply merged 1 commit into
canaryfrom
docs/cold-role-correction
Aug 2, 2026
Merged

docs(capacity): DriveRole::Cold is FROZEN storage, never the per-token streaming tier (#302 slice 0)#2115
joelteply merged 1 commit into
canaryfrom
docs/cold-role-correction

Conversation

@joelteply

Copy link
Copy Markdown
Contributor

BigMama's measurement: 130 MB/s HDD expert streaming = 156–544 s/token = unservable. The doc conflated the frozen tier with the hot per-token-paged tier (NVMe, governed by the upcoming NvmeServingTierPool). Doc-only.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo

…n streaming tier (#302 slice 0)

BigMama's measurement (2026-08-02): streaming an expert bank off a 130 MB/s
HDD = 156-544 s/token = unservable. The prior doc claimed Cold is where
'MoE expert sets are paged into VRAM on demand' — conflating the frozen
tier (source GGUFs, backups, unserved models) with the hot per-token-paged
tier, which MUST be NVMe. The doc now states the boundary the
NvmeServingTierPool (#302) governs: frozen until migrated up.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant