Unverified50% confidenceFactExact time
DeepSeek 1017's expert weights are already FP4 (4 bits per parameter), so conventional 4-bit quantization is of little help; the Engram memory table can be placed on SSD (reading only about 12KB per token), but the expert weights must reside in high-speed memory, because the router selects 6 of 384 experts per layer and makes a different selection for each token.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
DeepSeek New Version Hands-On: Same Price, Costs Slashed by 60%
bilibili枫叶边城10/18/2026
Related Entities
Related Claims
UnverifiedA user running a Threadripper platform with 512GB DDR4 memory achieved approximately 8 tokens/s running DeepSeek 671B by offloading expert layers to RAM.75% similarUnverifiedWhen streaming experts from an SSD, if the expert weight blocks are large (a single expert may be several hundred MB), the read granularity can approach sequential, and the performance loss is relatively controllable.73% similarUnverifiedAn agentic host requires at least 96 GB of unified memory as the entry-level threshold.73% similarUnverifiedThe runtime uses a four-tier storage architecture: the GPU maintains approximately 3.5 GB for attention/routers/shared experts and caches approximately 4,500 high-frequency experts; RAM stores all 24,576 experts; and the SSD stores approximately 28.8 GB of parameter lookup tables and N-Gram group tables.73% similarUnverifiedThe minimum configuration for running only DSH with the cloud-based DeepSeek API is a dual-core or higher CPU, 4 GB of memory, and more than 1 GB of free disk space; the daily recommended configuration is an i5/R5 quad-core with 8 GB or more of memory.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1059848API
curl https://kongchang.com/api/v1/knowledge/claims/1059848MCP
get_claim(id=1059848)