[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"report-2026-06-28":3,"JhFWIjeAsH":597,"l9u17HHQgW":612,"wOkmv5Wl4t":622,"yhwg6T4e9p":632,"nnGvesEkWu":642,"6qu44AT2aC":762,"dPvfmWRT7J":798,"VUcIXrc99l":814,"Qoi2Jull0W":830,"BiTpmKtArp":861,"EjUt9CqJch":897,"R1d49HNu3e":907,"BgXAMAFvYx":917,"iHRO7oQJuh":927,"5ZYPpHreHL":937,"mXMttXawRv":947,"UdmLaJj9yw":957,"JTnDBDPnFT":967,"fposgK6wYg":977,"YEqckks6KY":987,"8s3cmUt3ca":997,"k0YXyiFvMW":1007,"hyuoYb4d0S":1017,"vO7FJNPPdH":1148,"cg93aLlubf":1169,"5UdF5vsyeh":1195,"aoSt7i9AUz":1221,"mDeouFwyjz":1282,"zDDV8x5Vml":1328,"wbgBuUmf5K":1338,"LX2OSq72Nx":1348,"aSEordZCYL":1358,"niAB9K9SXN":1368,"367McZgmWB":1378,"Ou7tRalHiF":1388,"mnI4csw7Gk":1526,"vV3gvrwTiX":1537,"3w4OWp24TU":1548,"t5z9HmEkxt":1574,"2tFgpEkaa4":1600,"VPz3t9ZZMt":1724,"z8efDAlRme":1784,"0G86oWILzE":1809,"R1zLv34dFg":1826,"GgqSA2T4o3":1836,"ReQuVXvBkl":1846,"OIgrA9Nech":1856,"tENO9eMZCh":1866,"YkO87eRavt":1876,"zW0FNJCkmi":1886,"X43KGGfAnP":2037,"8tUlrxcmeM":2048,"Ew7zuEI5VV":2079,"dKLM8f3nhj":2105,"dP290aFbel":2116,"yZITe9wOjz":2232,"5lQPjTIc1O":2408,"cv19nGVPg6":2429,"DFiEs8W1KE":2450,"7UEr9QS1V5":2460,"dspsimY8pl":2470,"BljoIT5BvA":2518,"5KSrztx2p0":2534,"E3V75hJZqB":2550,"rzjkyDBmZc":2590,"0CwFKubGgL":2643,"K0qe7mANZq":2659,"CfkyECzldM":2675,"FZUMg1uped":2737,"oPHWl0FZoI":2753,"qOZeJQAJA4":2769,"qX2U2nEdIN":2813,"C3MauKIaTI":2895,"oZS8mzJscp":2905,"fHmv6X9KJc":2915,"YNlF8GQjbc":2975,"AobXE9lCvH":3006,"CeQRhIqYhr":3022,"HfR2vE2ygw":3105,"BIaB4EdLVS":3121,"j6QWuQD0YF":3137,"E2AsIj4yuL":3205,"Bpb5azcIIC":3221,"vQzHze2h4y":3237,"zcwtTZCnHi":3298,"VzCxW0mm60":3378,"PJXtxTtOli":3394,"05rhQr8AHY":3410,"QETrYm6AH0":3444,"tI6IDbSjo7":3525,"sjpFvbhBvc":3541,"raPHqnC1P7":3731},{"report":4,"adjacent":595},{"version":5,"date":6,"title":7,"sources":8,"hook":15,"deepDives":16,"quickBites":373,"communityOverview":580,"dailyActions":581,"outro":594},"20260216.0","2026-06-28","AI 趨勢日報：2026-06-28",[9,10,11,12,13,14],"academic","anthropic","community","github","media","nvidia","從政府管控到推測解碼，AI 今日同步上演存取戰與效能競賽，而半數用戶已靜靜將過半工作量交給模型。",[17,129,215,291],{"category":18,"source":10,"title":19,"subtitle":20,"publishDate":6,"tier1Source":21,"supplementSources":24,"tldr":45,"context":57,"policyDetail":58,"complianceImpact":59,"industryImpact":69,"timeline":70,"devilsAdvocate":94,"community":97,"hypeScore":116,"hypeMax":117,"adoptionAdvice":118,"actionItems":119},"policy","美國政府放行 Anthropic Mythos 模型，僅限「受信任」組織使用","出口禁令兩週後部分解封，動態白名單機制開啟前沿 AI 管制新時代",{"name":22,"url":23},"Semafor","https://www.semafor.com/article/06/27/2026/us-releases-powerful-anthropic-model-mythos-to-some-us-companies",[25,29,33,37,41],{"name":26,"url":27,"detail":28},"TechCrunch（Mythos 白名單解封報導）","https://techcrunch.com/2026/06/26/trump-admin-releases-anthropic-mythos-to-be-used-by-more-than-100-us-companies-agencies/","100 家以上美國組織獲批復存取 Mythos 5 的完整報導",{"name":30,"url":31,"detail":32},"TechCrunch（亞洲替代模型崛起）","https://techcrunch.com/2026/06/27/asian-ai-startups-launch-mythos-like-models-as-anthropics-export-ban-drags-on/","Sakana AI Fugu 與奇虎 360 系列模型搶占禁令空窗市場",{"name":34,"url":35,"detail":36},"The Decoder（Mythos 5 復存取確認）","https://the-decoder.com/anthropic-gets-us-approval-to-bring-back-claude-mythos-5/","美國政府正式批准 Anthropic 恢復 Mythos 5 存取的分析報導",{"name":38,"url":39,"detail":40},"The Decoder（Fable 5 即將解禁）","https://the-decoder.com/anthropics-fable-5-could-return-within-days-as-trump-administration-prepares-to-lift-restrictions/","五角大廈與 NSA 審核接近完成，Fable 5 最快數天內可能解禁",{"name":42,"url":43,"detail":44},"The Hill","https://thehill.com/policy/technology/5943549-anthropic-mythos-5-access/amp/","美國聯邦政府許可特選企業使用 Anthropic Mythos 模型的政策背景分析",{"tagline":46,"points":47},"前沿 AI 首度被納入武器等級出口管制，美國以「白名單」重塑全球模型存取規則",[48,51,54],{"label":49,"text":50},"政策","商務部長 Lutnick 簽署授權信，對 Mythos 5 建立動態白名單機制，超過 100 家美國企業與政府機構獲批；Fable 5 仍維持禁令，等待五角大廈與 NSA 審核，預計數天內有結果。",{"label":52,"text":53},"合規","管制邊界設在「組織層級」而非個人國籍，獲批組織內的非美國籍員工可使用 Mythos 5；但附錄 A 清楚標示僅限美國實體，外國機構（含盟友監管單位）全數排除在外。",{"label":55,"text":56},"影響","禁令空窗催生亞洲替代模型（Sakana AI Fugu、奇虎 360 系列），即使日後解禁，新建立的客戶關係可能形成持久壁壘；全球盟友對美國 AI 平台的信任也出現裂痕。","#### 章節一：Mythos 出口禁令的來龍去脈與國安考量\n\n2026 年 6 月 12 日，美國政府突然對 Anthropic 的 Mythos 5 與 Fable 5 祭出緊急出口管制，震驚全球 AI 業界。官方理由是擔憂 Mythos 5 在自動化漏洞挖掘與進攻性網路安全領域的能力過於強大，存在被惡意利用的實質風險。\n\n> **名詞解釋**\n> 越獄 (jailbreak) ：繞過 AI 模型的安全護欄，使其輸出原本受限的有害內容或協助惡意操作的技術手段。\n\n情報單位另外點名一家與中國資本有所關聯的韓國電信業者，認為其取得存取權將構成潛在的情報滲漏路徑，成為觸發本次緊急禁令的直接導火線。\n\nHN 社群的觀察者則提出另一種詮釋：禁令的底層邏輯更接近 1990 年代密碼學出口管制的歷史模式——政府真正意圖保護的，是確保前沿 AI 的網路偵察能力維持美國獨有的戰略優勢，而非單純防止外部攻擊。HN 用戶 2001zhaozhao 指出，這也解釋了為何 OpenAI 與 Anthropic 的模型同時受到限制的「不透明性」。\n\n#### 章節二：「受信任組織」機制的實際運作與限制\n\n約兩週後，商務部長 Lutnick 簽發授權信，建立起動態白名單機制。超過 100 家美國企業與政府機構被列入附錄 A(Annex A) 核准名單，條件是「營運並保衛關鍵基礎設施」。\n\n值得注意的是，已獲批組織內的非美國籍員工也同樣獲得授權，意味著管制邊界設定在「組織層級」而非「個人國籍」。然而觀察人士 @theobearman 指出，附錄 A 標題明確標示「Anthropic US Entities - Approved」，代表目前沒有任何外國機構——包括英國 UKAISI 監管單位——重新獲得 Mythos 5 存取授權。\n\nFable 5 並未出現在這份授權信中，五角大廈與 NSA 的審核尚未完成，預計最快「數天內」有結果。Lutnick 明確保留隨時修改名單的權力，使整套機制帶有高度政策不確定性。Anthropic 與 OpenAI 均已向政府遊說，希望以立法形式確立前沿模型審查框架，終結目前「個案核准」的法律灰色地帶。\n\n#### 章節三：亞洲 AI 新創趁禁令空窗搶推替代模型\n\n禁令空窗期間，亞洲 AI 新創迅速填補市場缺口，多家廠商加速推出定位為「Mythos 同類」的替代模型。\n\n東京 Sakana AI 推出 Fugu，定位為具備前沿能力且不受出口管制風險的替代選擇。中國網安公司奇虎 360 同步發布 Tulongfeng（專攻軟體漏洞偵測）與 Yitianzhen（自動化網路防禦），直接對標 Mythos 的核心應用場景。\n\nSakana AI 聯合創辦人 Ren Ito 表示：「AI 不應成為被囤積的技術，它應該是被共同開發的。」這句話折射出亞洲科技社群對美國出口管制的普遍情緒。\n\n業界觀察人士指出，本地替代模型已針對區域語言與使用習慣深度優化。即使禁令日後解除，這些新建立的客戶關係也可能形成持久競爭壁壘，讓美國 AI 廠商難以奪回失去的市佔。TechCrunch 報導直言：「美國 AI 實驗室可能永遠無法收復這個龐大市場。」\n\n#### 章節四：AI 出口管制對全球模型競爭格局的深遠影響\n\n此次事件標誌著一個新的監管先例：前沿 AI 模型首度被納入類似武器出口的政府審查體系，動態白名單取代了過去的開放存取模式。\n\nHN 社群對此產生的最深遠辯論，聚焦於全球市場互信的崩解問題。HN 上的歐洲評論者直言：「我們之所以依賴美國服務，是因為我們信任美國。」若美國可在無預警情況下切斷存取，當初基於互信建立的技術依賴將成為系統性脆弱點。\n\nAnthropicface 同時承受「以安全為由限制出口」與「因此損失海外收益」的雙重矛盾。其年化營收已達 470 億美元，海外市場的損失不可忽視，外界對其安全聲明與商業利益之間的矛盾也開始提出質疑。\n\n更長遠來看，這場出口管制競賽可能加速各國建立本土前沿模型的意願，進一步分裂全球 AI 生態系，形成「技術主權」優先於「開放協作」的新格局，且這個趨勢一旦啟動將難以逆轉。","#### 核心條款\n\n商務部長 Howard Lutnick 於 2026 年 6 月 26-27 日簽署授權信，解除對 Mythos 5 的部分出口限制，批准超過 100 家美國企業與聯邦機構存取該模型。授權條件明確限定為「營運並保衛關鍵基礎設施的組織」，且附有核准名單附錄 (Annex A) ，並保留隨時增刪的彈性，等同動態白名單機制。\n\n#### 適用範圍\n\n管轄對象為全球所有存取 Mythos 5 的非美國合作夥伴；解禁後僅限附錄名單內的美國組織，外國機構（包括 UKAISI 等盟友監管單位）目前全數排除在外。獲批組織內的非美國籍員工也一併納入授權，但管制邊界是組織而非個人層級。Fable 5 仍維持禁令，需待五角大廈與 NSA 額外審核。\n\n#### 執法機制\n\n目前無正式法律框架，依商務部長個案簽署授權信方式執行。Anthropic 與 OpenAI 均已積極遊說，希望以立法形式確立前沿模型審查框架，終結「個案核准」的法律灰色地帶。授權信保留隨時撤銷的彈性，形成高度法律不確定性。",[60,63,66],{"label":61,"markdown":62},"工程改造需求","企業需在存取 Mythos 5 前完成身份驗證與使用追蹤基礎設施建設，確保使用紀錄可供政府稽查。\n\n非美國籍員工雖獲授權使用，仍建議建立完整的使用者行為日誌 (audit log) 以降低合規風險，並定期確認自身組織是否仍在附錄 A 的有效名單中。",{"label":64,"markdown":65},"合規成本估計","短期成本主要為法律顧問費用（解讀授權條件、協助申請列入白名單）與合規系統整合費用。\n\n若立法框架確立，預計需設置專職 AI 合規官 (AI Compliance Officer) 職位。授權信隨時可撤銷的特性，也意味著企業必須持續維護備援方案，形成多廠商架構的隱性長期成本。",{"label":67,"markdown":68},"最小合規路徑","1. 確認組織是否符合「關鍵基礎設施營運商」定義（能源、金融、醫療、電信等）\n2. 向 Anthropic 提交組織資訊，申請列入附錄 A 核准名單\n3. 建立使用者存取日誌與審計機制，以備政府查核\n4. 持續監控政策動態——授權信可隨時異動，需設立預警機制","#### 直接影響者\n\nAnthropicfacing 本身首當其衝——Mythos 5 禁令期間直接流失海外客戶收益，估計影響其 470 億美元年化營收的相當比例。以 Mythos 5 為核心業務的美國網路安全廠商，在禁令期間被迫中斷服務或轉向替代方案，部分合約可能永久流失。\n\n#### 間接波及者\n\n依賴 Anthropic API 的歐洲與亞洲中小型 SaaS 廠商在禁令期間無法取得模型存取，部分已展開遷移評估。Sakana AI(Fugu) 與奇虎 360（Tulongfeng、Yitianzhen）等亞洲替代模型廠商則意外受益，獲得加速吸客的時間視窗，潛在客戶關係的黏著度已開始形成。\n\n#### 成本轉嫁效應\n\n最終使用者端的衝擊主要體現在服務中斷與替代方案的遷移摩擦成本。若禁令長期化或擴大至更多模型，依賴美國 AI 供應商的企業將面臨「地緣政治風險溢價」的新採購考量，歐洲與亞洲監管機構也可能以此為契機，加速推動 AI 供應鏈本土化政策。",[71,75,78,81,86,90],{"date":72,"text":73,"phase":74},"2026-06-12","美國政府突發緊急出口禁令，Mythos 5 與 Fable 5 全面限制非美國合作夥伴存取","past",{"date":76,"text":77,"phase":74},"2026-06-26","商務部長 Lutnick 簽署授權信，解除 Mythos 5 對超過 100 家美國組織的限制，附錄 A 白名單正式生效",{"date":79,"text":80,"phase":74},"2026-06-27","Anthropic 公開確認正在「快速恢復」授權組織的存取，持續與政府談判擴大 Mythos 5 覆蓋範圍",{"date":82,"label":83,"text":84,"phase":85},"短期（數天內）","短期","五角大廈與 NSA 完成 Fable 5 安全審核，最快數天內可能解禁，Fable 5 有望恢復一般使用","future",{"date":87,"label":88,"text":89,"phase":85},"中期（3-6 月）","中期","Anthropic 與 OpenAI 推動立法，將前沿模型出口審查納入法律框架；各國開始評估 AI 供應鏈本土化策略以降低依賴風險",{"date":91,"label":92,"text":93,"phase":85},"後續觀察","觀察","亞洲替代模型市佔率變化、歐洲盟友對美國科技依賴的政策回應、前沿 AI 出口管制是否擴大至更多廠商或模型類別",[95,96],"出口管制真的能阻止惡意行為者嗎？越獄技術與地下黑市的存在意味著模型能力終將擴散，禁令或許只是讓盟友損失競爭優勢，對真正的攻擊者幾乎毫無阻擋。","動態白名單機制本身可能製造不公平競爭——獲批組織享有 Mythos 5 先行者優勢，未獲批的競爭對手被系統性排除，這反而讓「國安理由」成為市場壟斷的隱性工具。",[98,102,105,109,113],{"platform":99,"user":100,"quote":101},"Hacker News","wrsh07(HN)","政府一直不太擅長遮掩真實意圖，但這次倒也算公平！本來希望有其他人先提出這個想法，不過確實是個好思路。",{"platform":99,"user":103,"quote":104},"2001zhaozhao(HN)","非常同意，這是個合理的論點。如果是真的，就解釋了整件事的不透明性，也說明了為何 OpenAI 與 Anthropic 的模型如今同時受到限制。",{"platform":106,"user":107,"quote":108},"X","David Sacks（白宮 AI 與加密貨幣顧問；創投家）","我與政府內外多位人士深談了目前 Anthropic 的處境。我認為屬實的情況是：Anthropic 本週稍早在商業名稱 Fable 下公開發布了其 Mythos 系列模型。",{"platform":110,"user":111,"quote":112},"Bluesky","thesynthwire.bsky.social（Bluesky，4 upvotes）","亞洲 AI 新創不打算等了。隨著 Anthropic 出口限制持續，亞洲各地正湧現出新的「Mythos 同類」模型——彰顯出當存取受限時，全球 AI 競賽的適應速度之快。",{"platform":106,"user":114,"quote":115},"@theobearman(X)","這裡有兩件事讓我注意到：附錄 A（可重新存取 Mythos 5 的核准實體名單）標題是「Anthropic US Entities - Approved（已批准的 Anthropic 美國實體）」。目前看來沒有任何外國機構——包括 UKAISI 在內——重新獲得 Mythos 5 的存取授權。",4,5,"追整體趨勢",[120,123,126],{"type":121,"text":122},"Try","若所在組織屬於關鍵基礎設施營運商（能源、金融、醫療、電信），立即聯繫 Anthropic 客戶代表，確認是否已列入附錄 A 或申請程序。",{"type":124,"text":125},"Build","建立多 AI 供應商備援架構，將核心工作流程同時測試於 Anthropic、OpenAI 與本地開源模型，降低單一供應商的地緣政治中斷風險。",{"type":127,"text":128},"Watch","密切追蹤 Fable 5 解禁進展、Anthropic 與 OpenAI 遊說立法結果，以及歐洲盟友是否透過外交壓力取得豁免條款或另立等效框架。",{"category":130,"source":11,"title":131,"subtitle":132,"publishDate":6,"tier1Source":133,"supplementSources":136,"tldr":161,"context":173,"perspectives":174,"practicalImplications":186,"socialDimension":187,"devilsAdvocate":188,"community":191,"hypeScore":116,"hypeMax":117,"adoptionAdvice":207,"actionItems":208},"discourse","Post-Training 革命：小型本地模型如何透過後訓練逼近商用大模型","Cursor 承認基於 Kimi K2.5，揭開業界後訓練策略的秘密——垂直訓練的 ROI 正在超越大模型 API",{"name":134,"url":135},"r/LocalLLaMA — What should I do? - consider post-training","https://redlib.perennialte.ch/r/LocalLLaMA/comments/1ugg1dm/what_should_i_do_consider_posttraining/",[137,141,145,149,153,157],{"name":138,"url":139,"detail":140},"Cursor admits its new coding model was built on top of Moonshot AI's Kimi — TechCrunch","https://techcrunch.com/2026/03/22/cursor-admits-its-new-coding-model-was-built-on-top-of-moonshot-ais-kimi/","報導 Cursor 承認 Composer 2 以 Kimi K2.5 為底座，並引述 VP 說明訓練算力比例",{"name":142,"url":143,"detail":144},"A technical report on Composer 2 · Cursor Blog","https://cursor.com/blog/composer-2-technical-report","Cursor 官方技術報告，說明 outcome-based reward 設計與 GRPO 變體訓練方法",{"name":146,"url":147,"detail":148},"How Kimi, Cursor, and Chroma Train Agentic Models with RL — philschmid.de","https://www.philschmid.de/kimi-composer-context","深度分析三家公司的 RL 後訓練策略，含 PARL 獎勵函數設計與三層獎勵信號細節",{"name":150,"url":151,"detail":152},"Reward Modeling | RLHF and Post-Training Book by Nathan Lambert","https://rlhfbook.com/c/05-reward-models","系統性介紹後訓練中的獎勵模型設計，比較 DPO、ORPO、KTO 等主流演算法",{"name":154,"url":155,"detail":156},"Gemma 3 Technical Report — arXiv","https://arxiv.org/html/2503.19786v1","說明 Gemma 3 系列採用知識蒸餾後訓練策略，Gemma3-4B-IT 比肩 Gemma2-27B-IT 的實驗結果",{"name":158,"url":159,"detail":160},"Supervised Fine-Tuning versus Reinforcement Learning: Post-Training Methods — arXiv","https://arxiv.org/html/2603.13985v1","系統比較 SFT 與 RL 後訓練方法的優劣與適用場景",{"tagline":162,"points":163},"Cursor 用 Kimi K2.5 做後訓練，3/4 的算力是自己投入的——這才是真正的工程策略",[164,167,170],{"label":165,"text":166},"爭議","Cursor Composer 2 承認以 Kimi K2.5 為底座後訓練，VP 表示 3/4 算力來自自行訓練，引發業界對「何謂自研模型」的邊界討論。",{"label":168,"text":169},"實務","後訓練技術（DPO、ORPO、KTO、PARL）日趨普及，Gemma 系列配合 TraceGen 等工具讓中小型團隊也能低成本實驗垂直領域後訓練。",{"label":171,"text":172},"趨勢","Chroma 20B 在向量檢索任務上達到 10 倍速度提升並大幅降本，印證「垂直訓練策略 > 暴力堆算力」的社群共識正逐漸主流化。","#### 章節一：Cursor 背後的秘密——Kimi K2 後訓練版的啟示\n\n2026 年 3 月，Cursor 發佈 Composer 2 並宣稱為「自研模型」，三天後即因社群壓力承認底座為 Moonshot AI 的開源模型 Kimi K2.5。\n\n這場爭議揭示的核心命題並非「抄捷徑」，而是一種工程策略的正當性：以成熟開源基底為起點，投入大量特定領域訓練資源，最終打造出比通用商業大模型更適合特定場景的產品。\n\nCursor VP 明確說明，最終模型中僅有約 1/4 的算力來自 Kimi K2.5 基底，其餘 3/4 均為 Cursor 自行訓練投入——包括程式碼專屬資料的持續預訓練 (continued pretraining) 以及大規模強化學習 (RL) 以最佳化端對端 agent 表現。\n\nr/LocalLLaMA 社群的直覺因此得到印證：「用適合自己 use case 的後訓練小模型，比依賴面向大眾調整的大型商業模型，更有針對性優勢。」Cursor 的案例讓這個社群信念首次獲得主流科技媒體的具體佐證。\n\n#### 章節二：Post-Training 的核心技術與獎勵函數設計\n\nKimi 採用自行設計的 PARL(Parallel-Agent Reinforcement Learning) 框架，透過三層獎勵信號協同訓練。主目標為任務成功的 performance reward；輔助設有 parallelism reward 防止 orchestrator 退化為序列執行；finish reward 則防止「偽並行」——即大量生成 sub-agent 卻無實質分工的問題。\n\n> **名詞解釋**\n> PARL(Parallel-Agent Reinforcement Learning) ：一種針對多 agent 協作設計的強化學習框架，透過多重獎勵信號同時訓練 orchestrator 的並行決策能力，而非僅最佳化單一任務完成率。\n\n這些輔助獎勵在訓練後期逐步退火 (annealed to zero) ，使最終策略純粹以性能為準。\n\nCursor Composer 2 則採取不同路線：從真實用戶互動中提取 outcome-based reward，在與生產環境完全相同的工具、prompt 和系統訊息下訓練，最小化 train/serve 差距。其 policy gradient 變體近似 GRPO，但移除了長度標準化偏差與 advantage normalization。\n\n當前社群主流的後訓練方案已從傳統 PPO 移轉：DPO 直接從偏好對最佳化，無需獨立獎勵模型；ORPO 將 SFT 與偏好最佳化合而為一，適合小資料集；KTO 只需二元反饋訊號，更易收集標注資料。\n\n#### 章節三：實戰資源與工具鏈：從 Gemma 到 TraceGen\n\n在 r/LocalLLaMA 討論串中，u/HVACcontrolsGuru 分享了以 Gemma 系列為基底進行蒸餾與後訓練的實測心得，並特別提到 TraceGen 工具——用於從較大模型萃取推理軌跡 (reasoning traces) ，進而蒸餾到較小的 Gemma 模型中，適合非程式碼領域的垂直場景。\n\nGemma 3 系列本身的後訓練策略已相當完善：從更大的 instruct 模型中每個 token 取樣 256 個 logits 進行知識蒸餾，搭配 BOND、WARM、WARP 等 RL 演算法，使 Gemma3-4B-IT 在數學與多語言能力上比肩 Gemma2-27B-IT——即以 4B 參數模型達到過去 27B 模型的水準。\n\n> **白話比喻**\n> 知識蒸餾就像讓見多識廣的老師（大模型）在考試中逐題說明思路，讓學生（小模型）不只學答案，而是學推理過程——最終學生雖然「腦容量」小，但在老師擅長的題型上表現可以不輸老師。\n\n對於希望入門後訓練的開發者，Gemma 3 提供了良好的起點：模型授權開放、社群資源豐富，且有足夠的參數空間可供後訓練調整推擠。\n\n#### 章節四：小模型後訓練 vs. 大模型 API——成本效益與適用場景\n\n三個真實案例共同指向同一結論：「垂直訓練策略 > 暴力堆算力」。Cursor Composer 2 以 3/4 的自行訓練算力，在程式碼 agent 任務上達到與大型 API 模型相近的成本效益；Chroma 20B 在向量檢索任務上速度提升 10 倍、成本大幅降低；Kimi K2.5 作為底座讓 Cursor 得以快速建立高度特化的 coding agent。\n\n這三個案例的共同前提是「有明確的垂直場景」。對於 coding agent、向量檢索、特定領域推理等任務，後訓練小模型的 ROI 遠高於直接呼叫通用商業大模型 API。正如 u/entsnack 所言：「大型商業模型是為大眾設計的，不是為你的特殊 use case——這正是後訓練小模型的切入點。」\n\n值得注意的是，後訓練的「秘方」仍是業界高度保密的競爭優勢。Cursor 承認基底後，具體的獎勵函數設計、資料配方、訓練超參數仍未完全公開。這也意味著社群在復刻商業後訓練效果時，仍需大量實驗與迭代。",[175,179,183],{"label":176,"color":177,"markdown":178},"正方立場","green","後訓練小模型可以在特定場景超越大型商業模型，且成本效益更高。\n\nCursor Composer 2 的案例提供了最直接的證據：以 Kimi K2.5 為底座，投入 3/4 的自行訓練算力，最終在程式碼 agent 任務上達到與更大 API 模型相近的成本效益比。Chroma 20B 在向量檢索任務上的 10 倍速度提升，更是「垂直訓練」優勢的具體量化。\n\n核心論點在於：大型商業模型的後訓練目標是面向最大公約數的用戶群，必然在特定場景上做出妥協。垂直後訓練則可針對特定任務設計獎勵函數，優化 train/serve 差距。擁有明確垂直場景的團隊，後訓練小模型是目前 ROI 最高的策略選項。",{"label":180,"color":181,"markdown":182},"反方立場","red","後訓練並非萬靈丹：基底模型的知識上限、訓練資源需求、以及「秘方」保密性，都是不可忽視的障礙。\n\nHN 用戶 SwellJoe 親身實驗了對 Gemma 4 進行後訓練以模仿自己的寫作風格，但仍坦承「LLM 寫的文字還是看得出來」。crawshaw.io(David Crawshaw) 更直指核心問題：「商業 LLM 的後訓練過程讓它們喪失了寫作能力——18 個月前的開放基底模型寫得更好。」\n\n此外，後訓練的「秘方」——包括獎勵函數設計、資料配方、訓練超參數——仍是業界高度保密的競爭優勢。即使底座開源，複製頂級商業後訓練效果需要的工程深度遠超社群想像。\n\n缺乏專業 ML 工程師和大量高品質的 domain-specific 訓練資料，「後訓練小模型」可能只是個耗費資源卻效果有限的實驗。",{"label":184,"markdown":185},"中立／務實觀點","後訓練與大模型 API 並非非此即彼，而是取決於場景清晰度與工程能力。\n\n若任務邊界清晰、有大量高品質標注資料、且團隊具備 ML 訓練能力，後訓練小模型（DPO/ORPO/KTO 入門，PARL/GRPO 進階）是值得投資的路線。反之，若任務多元、資料稀缺、或工程資源有限，大模型 API 仍是最低摩擦的選擇。\n\nHN 用戶 anon373839 提出一個值得關注的觀點：GLM-5.2 的完整 RL 訓練（讓它在 agentic 任務上可靠的關鍵部分）只花了兩天——這意味著後訓練的邊際成本正在快速下降。\n\n隨著工具鏈（TraceGen、Unsloth、trl）持續成熟，「後訓練的門檻」問題可能在 12-18 個月內有顯著改善，現在是學習這套方法的好時機，但未必是大量投入生產的最佳時機。","#### 對開發者的影響\n\n後訓練不再是大公司的專利，但仍需要明確的技術路線選擇：DPO 適合有偏好對資料的場景；ORPO 適合資料量小但需要同時最佳化 SFT 與偏好的情境；KTO 適合只能收集二元反饋（好／不好）的生產環境。\n\n獎勵函數設計是核心工程挑戰。u/entsnack 提醒：即使是訓練模型玩 Wordle 這樣的小任務，獎勵函數的設計本身就非平凡——但跑通後的成就感也正比於此。開發者應從小任務入手，建立對訓練動態的直覺，再擴展到生產場景。\n\n#### 對團隊／組織的影響\n\nCursor 案例改變了「build vs. buy」的決策框架：在有明確垂直場景的情況下，開源底座加後訓練的路線可以在成本效益上超越直接呼叫商業 API。\n\n這意味著 ML 工程師和訓練基礎設施的價值正在上升。對於 AI-first 產品公司，在 prompt engineering 之外建立後訓練能力，可能是未來 12-24 個月的關鍵差異化投資。但前提是有明確的任務邊界和足夠的領域資料。\n\n#### 短期行動建議\n\n- 用 Gemma 3 4B 搭配 trl 函式庫跑第一個 DPO 實驗：從 HuggingFace 取得偏好資料集，體驗獎勵函數設計的核心挑戰\n- 使用 TraceGen 從大模型萃取推理軌跡，作為蒸餾到小模型的訓練資料起點\n- 在設計獎勵函數前，先花 2-3 週收集真實用戶行為資料，確認任務邊界夠清晰","#### 產業結構變化\n\nCursor 事件開啟了一個「模型透明度」的討論：當底座開源、後訓練深度成為核心競爭力時，「自研模型」的定義邊界在哪裡？這個問題不只是語義之爭——它直接影響投資者估值邏輯、用戶信任基礎，以及未來 AI 產品的授權模式。\n\n從更宏觀的角度看，後訓練技術的普及正在降低 AI 能力的門檻：中小型公司在特定垂直領域追上前沿的路徑變得更清晰。Chroma 20B 的案例顯示，即使是非 AI-first 的基礎設施公司，也能透過後訓練在利基場景建立技術護城河。\n\n#### 倫理邊界\n\n後訓練的「底座透明度」問題觸及更深層的倫理議題：當產品宣稱「自研」但實際上建立在他人開源貢獻之上，開源社群的貢獻如何被承認？Moonshot AI 選擇以商業授權方式合作（透過 Fireworks AI），提供了一個雙方受益的範本，但並非所有開源底座都有相同的商業化設計。\n\n#### 長期趨勢預測\n\n根據目前討論趨勢，可以預期「多模型生態」將加速成型：少數基底模型（Gemma、Kimi、Llama 系列）作為廣受採用的底座，大量垂直後訓練版本在其上繁殖，服務各自的利基市場。crawshaw.io 的預言——「我們需要一個多模型的未來」——正在從願景轉為現實。\n\nAndrew Ng 等教育者開始系統化教授後訓練課程，意味著這套知識正從業界秘方走向工程常識。後訓練能力的護城河將逐漸轉向資料質量與場景深度，而非單純的工程技術壁壘。",[189,190],"後訓練的核心「秘方」——獎勵函數設計、資料配方、訓練超參數——仍高度保密，社群能取得的公開資訊可能只是冰山一角，實際複製商業效果的難度遠被低估。","Cursor 事件顯示「自研」邊界模糊，若後訓練變成主流策略，頭部基底模型的話語權只會更加集中——Kimi、Gemma、Llama 背後仍是少數大公司，並非真正的去中心化。",[192,196,198,201,204],{"platform":193,"user":194,"quote":195},"Reddit r/LocalLLaMA","u/entsnack","Cursor 的模型確實是後訓練版的 Kimi K2。我真的相信，一個經過後訓練的小型本地 LLM，可以在表現上媲美沒有後訓練的大型商業模型——因為那些商業模型是為大眾設計的，不是為你的特殊使用場景。但後訓練的秘方通常是業界嚴守的機密。",{"platform":193,"user":194,"quote":197},"就算只是後訓練一個 LLM 來做玩 Wordle 這類有趣的事情也很好玩！這並不簡單，因為你需要設計獎勵函數。但一旦讓它跑起來，成就感十足。",{"platform":193,"user":199,"quote":200},"u/HVACcontrolsGuru","我分享一些我學到並一直在測試評估的資源，主要聚焦在 Gemma 系列：TraceGen 工具——我一直在嘗試把較大的模型蒸餾進 Gemma，針對一些非程式碼的領域。這些模型有相當大的頭室可以調整，E4B 也夠好用來學習和練習。",{"platform":110,"user":202,"quote":203},"crawshaw.io（David Crawshaw，75 upvotes）","我確信，商業 LLM 的後訓練過程讓它們喪失了寫作能力。18 個月前的開放基底模型寫得更好。我甚至無法信任一個「前沿」模型來撰寫開發文件。這更加印證了我們需要一個多模型的未來。",{"platform":99,"user":205,"quote":206},"HN 用戶 anon373839","如果大型模型的資料管道關閉，開放 LLM 研究將有強大誘因聚焦於後訓練，以刷新過時的基底模型。而且後訓練本來就比預訓練便宜且快速得多。我相當驚訝地發現，GLM-5.2 完整的 RL 訓練——讓它在 agentic 任務上可靠的那部分——只花了兩天。","值得一試",[209,211,213],{"type":121,"text":210},"用 Gemma 3 4B 搭配 trl 函式庫跑第一個 DPO 實驗：從 HuggingFace 取得偏好資料集，訓練一個針對自己使用場景的模型，直接體驗獎勵函數設計的核心挑戰。",{"type":124,"text":212},"若有明確垂直場景（程式碼生成、特定領域 QA、向量檢索），評估以 Kimi K2.5 或 Gemma 3 27B 為底座、搭配 TraceGen 蒸餾訓練資料，打造比通用 API 更具成本效益的 task-specific 模型。",{"type":127,"text":214},"關注 DeepLearning.AI 與 BanghuaZ 合作的後訓練課程（SFT、DPO、online RL 三大主題），以及 Cursor Composer 2 技術報告後續更新——目前最公開的商業後訓練案例，值得持續追蹤。",{"category":216,"source":9,"title":217,"subtitle":218,"publishDate":6,"tier1Source":219,"supplementSources":222,"tldr":239,"context":251,"mechanics":252,"benchmark":253,"useCases":254,"engineerLens":263,"businessLens":264,"devilsAdvocate":265,"community":268,"hypeScore":116,"hypeMax":117,"adoptionAdvice":207,"actionItems":284},"tech","DSpark 推測解碼框架：大幅加速 LLM 推理的新方法","DeepSeek 以半自回歸架構與置信度排程驗證，讓同等硬體吞吐量最高提升 400%",{"name":220,"url":221},"DSpark 論文（arXiv：2606.19348）","https://github.com/deepseek-ai/DeepSpec/blob/main/DSpark_paper.pdf",[223,227,231,235],{"name":224,"url":225,"detail":226},"Hacker News 討論串","https://news.ycombinator.com/item?id=48696585","社群對 DSpark 開源動機的地緣政治討論",{"name":228,"url":229,"detail":230},"MarkTechPost：DSpark 發布報導","https://www.marktechpost.com/2026/06/27/deepseek-releases-dspark-a-speculative-decoding-framework-that-accelerates-deepseek-v4-per-user-generation-60-85-over-mtp-1/","V4 Flash 生產數據報導",{"name":232,"url":233,"detail":234},"Crypto Briefing：DSpark 推理加速分析","https://cryptobriefing.com/deepseek-dspark-faster-inference/","分散式算力網路的單位經濟學影響分析",{"name":236,"url":237,"detail":238},"AI Weekly：DeepSpec 開源報導","https://aiweekly.co/alerts/deepseek-open-sources-deepspec-speculative-decoding-stack","DeepSpec MIT 授權開源與跨生態相容性說明",{"tagline":240,"points":241},"推測解碼進入硬體感知時代：DSpark 讓相同 GPU 多服務 51–400% 的請求",[242,245,248],{"label":243,"text":244},"技術","DSpark 以半自回歸架構結合置信度排程驗證，接受 token 長度比 Eagle3 提升 26.7–30.9%，比 DFlash 提升 16.3–18.4%，數字來自線上生產流量而非實驗室沙盒。",{"label":246,"text":247},"成本","V4 Flash 每用戶生成速度比 MTP-1 快 60–85%，整體吞吐量提升 51–400%；同等硬體可服務更多請求，從根本上改變 GPU 租賃的單位經濟學。",{"label":249,"text":250},"落地","無需重訓基礎模型，checkpoint 直插 V4 推理棧；DeepSpec 以 MIT 授權開源，已支援 Gemma 與 Qwen，任何團隊均可為自有模型訓練草稿頭。","#### 章節一：推測解碼的原理與現有方法瓶頸\n\n推測解碼的核心邏輯是以「小帶大」：由輕量草稿模型批量提議一組候選 token，再由大型目標模型一次前向傳播驗證整個批次，透過拒絕採樣保留有效前綴，在輸出品質無損的前提下減少串行解碼步數。\n\n然而傳統方案存在兩大瓶頸。其一，草稿品質越高，驗證長度越難預測，GPU 批次排程效率下降；其二，平行生成位置間的條件依賴被完全忽略，導致接受率在長序列時顯著衰減。\n\nEagle-3 與 DFlash 雖已改善部分問題，但仍以固定驗證長度為主，無法根據硬體負載動態調整。這正是 DSpark 試圖填補的缺口——讓草稿批次長度真正「感知」目標模型的即時驗證能力。\n\n#### 章節二：DSpark 的架構創新與技術突破\n\nDSpark(Confidence-Scheduled Speculative Decoding with Semi-Autoregressive Generation) 並非新模型，而是疊加在現有 DeepSeek-V4 權重上的推理加速模組，無需重新訓練基礎模型即可部署。\n\n其核心架構分為兩個協同組件：**平行草稿主幹**（DFlash 風格）對所有位置同步生成基礎 logits；**序列注意力頭**(Sequential Head) 以低秩分解 (rank 256) 在採樣前為每個位置疊加前綴條件偏置，預設採用僅依賴前一 token 的 Markov 變體，大幅壓縮計算開銷。\n\n> **名詞解釋**\n> 低秩分解 (Low-Rank Decomposition) ：將一個大型矩陣近似拆解為兩個小矩陣相乘，大幅減少參數量與計算成本，常用於模型壓縮與高效注意力機制。\n\n更關鍵的創新在於**置信度排程驗證**：一個置信度預測頭以 Sequential Temperature Scaling 校準，估算 token 存活概率，將預測誤差從 3–8% 壓縮至約 1%。搭配**硬體感知前綴排程器**，閒置時延長驗證批次、高負載時縮短批次，草稿長度從 4 延伸至 16 token 時每輪延遲僅增加 0.2–1.3%。\n\n#### 章節三：基準測試與實際加速倍率\n\n離線評估中，DSpark 在 Qwen3 系列模型上相比 Eagle3 的接受 token 長度提升 26.7–30.9%，相比 DFlash 提升 16.3–18.4%。DeepSpec 評估框架覆蓋 GSM8K、MATH500、HumanEval、LiveCodeBench 等九項標準基準，全部開源供社群複現。\n\n生產環境的數字更為直接：V4 Flash 每用戶生成速度比 MTP-1 基線快 60–85%，Pro 版快 57–78%；依並發程度不同，整體吞吐量提升幅度在 51% 至 400% 之間。這些數字均來自已部署的線上流量，而非實驗室沙盒。\n\n> **名詞解釋**\n> MTP-1(Multi-Token Prediction 1) ：一次前向傳播僅預測 1 個 token 的基礎自回歸解碼策略，是本論文的比較基線。\n\n#### 章節四：對生產環境 LLM 部署的實務影響\n\nDSpark checkpoints 無需重新訓練基礎模型，可直接插入現有 V4 推理棧，並已在 Gemma 與 Qwen 模型上驗證跨生態系相容性。DeepSpec 以 MIT 授權開源，讓任何團隊都能為自己的模型訓練推測解碼草稿頭。\n\n對分散式算力網路（如 Akash、io.net）而言，同等硬體可服務的請求數大幅提升，從根本上改變 GPU 租賃的單位經濟學。HN 評論者 lwansbrough 直接點出「這不是貪婪的問題，而是國家安全的問題」——意指中國 AI 實驗室持續的開放發布策略，已成為重塑全球算力競爭格局的政策工具，而非單純的技術慷慨。","DSpark 的設計目標是在不動基礎模型的前提下，最大化每次驗證批次的有效 token 接受數。傳統推測解碼的草稿模型為全平行生成，忽略位置間條件依賴；DSpark 以「半自回歸」架構在速度與精度之間取得平衡。\n\n#### 機制 1：半自回歸生成架構\n\n平行草稿主幹同步為所有草稿位置生成基礎 logits，保留高吞吐量優勢。序列注意力頭 (Sequential Head) 以低秩分解 (rank 256) 在採樣前為每個位置疊加前綴條件偏置，使後位置的預測能感知前位置的生成結果，顯著提升草稿序列的語義連貫性。預設採用 Markov 變體（僅依賴前一 token），計算開銷遠低於全序列自回歸草稿。\n\n#### 機制 2：置信度排程驗證\n\n一個獨立的置信度預測頭以 Sequential Temperature Scaling 校準，估算每個草稿 token 被目標模型接受的概率。校準後預測誤差從 3–8% 壓縮至約 1%，讓排程器能可靠決定哪些序列應延長草稿批次（高置信度）、哪些應提前截止以避免浪費驗證算力（低置信度）。\n\n> **名詞解釋**\n> Sequential Temperature Scaling：一種後處理校準技術，透過學習一個溫度參數調整模型輸出的機率分布，使預測置信度與實際準確率對齊。\n\n#### 機制 3：硬體感知前綴排程器\n\n排程器即時感知 GPU 負載狀態：閒置時延長驗證批次（草稿長度可達 16 token），高負載時縮短批次以降低排隊延遲。實測顯示草稿長度從 4 延伸至 16 token 時每輪延遲僅增加 0.2–1.3%，打破「更長草稿等於更高延遲」的傳統假設。這種動態策略使系統在不同並發等級下都能保持吞吐量最大化。\n\n> **白話比喻**\n> 想像一位服務生（草稿模型）一次端上 10 道菜候選，廚師長（目標模型）掃一眼就決定哪道真的上桌。DSpark 的創新是：服務生先和旁邊的同事確認每道菜的搭配是否合理（序列注意力頭），再根據廚師長目前的忙碌程度決定一次端幾道（硬體感知排程），讓廚師長永遠不在等待，也不被淹沒。","#### 離線基準比較（Qwen3 系列）\n\nDSpark 接受 token 長度相比 Eagle3 提升 26.7–30.9%，相比 DFlash 提升 16.3–18.4%。DeepSpec 評估框架覆蓋九項標準基準（GSM8K、MATH500、HumanEval、LiveCodeBench 等），全部開源供社群複現。\n\n#### 生產流量實測\n\n- V4 Flash：每用戶生成速度比 MTP-1 快 **60–85%**\n- V4 Pro：每用戶生成速度比 MTP-1 快 **57–78%**\n- 整體吞吐量：依並發程度提升 **51%–400%**\n\n草稿長度從 4 延伸至 16 token 時，每輪延遲僅增加 0.2–1.3%，驗證硬體感知排程器在高負載下的低開銷特性。",{"recommended":255,"avoid":260},[256,257,258,259],"高並發 LLM API 服務（並發越高，動態排程的吞吐量紅利越顯著）","成本敏感的推理部署（不升級 GPU 即可提升有效服務容量）","分散式算力網路（Akash、io.net 等按需 GPU 租賃，單位算力產出直接改善）","跨模型推測解碼研究（DeepSpec 已支援 Gemma、Qwen，可作為訓練框架基礎）",[261,262],"低並發批次離線任務（動態排程收益有限，固定長度方案更可預測）","草稿頭與基礎模型版本不對齊的環境（混用版本會導致接受率暴跌至基線以下）","#### 環境需求\n\nDSpark checkpoints 已上傳至 Hugging Face（DeepSeek-V4-Pro-DSpark 與 DeepSeek-V4-Flash-DSpark），以標準 transformers 或 vLLM 載入即可。DeepSpec 訓練代碼庫以 MIT 授權開源，支援 Python 3.10+ 環境，依賴 PyTorch 2.x，推薦搭配 vLLM 或 SGLang 作為推理後端。\n\n#### 最小 PoC\n\n```bash\npip install vllm\npython -m vllm.entrypoints.openai.api_server \\\n  --model deepseek-ai/DeepSeek-V4-Flash-DSpark \\\n  --speculative-model deepseek-ai/DeepSeek-V4-Flash-DSpark-Draft \\\n  --num-speculative-tokens 8\n```\n\n#### 驗測規劃\n\n部署後建議以 DeepSpec 內附的 HumanEval 與 MATH500 腳本驗證接受率是否落在論文基準範圍（比 Eagle3 提升 26.7–30.9%）。生產環境需同步監控 P50/P99 TTFT（首 token 延遲）與每秒 output token 數 (TPS) ，確認吞吐量提升與延遲 SLA 同步達標。\n\n#### 常見陷阱\n\n- 草稿頭與基礎模型版本必須嚴格對齊——混用不同 checkpoint 版本會導致接受率暴跌至 Eagle3 基線以下\n- 硬體感知排程器預設為 A100/H100 調校，在 V100 或消費級 GPU 上需重新調整 batch size 上限\n- DeepSpec 訓練目前僅提供 Gemma 與 Qwen 的配置範例；其他模型系列需自行撰寫草稿頭訓練腳本\n\n#### 上線檢核清單\n\n- 觀測：接受 token 率 (per-request) 、草稿批次長度分布、GPU 利用率熱圖\n- 成本：草稿頭推理增量記憶體（rank 256 低秩頭約 +2–4 GB VRAM per GPU）、自訓草稿頭需額外算力預算\n- 風險：跨 checkpoint 版本的草稿頭相容性、高並發下動態排程的尾延遲抖動 (P99)","#### 競爭版圖\n\n- **直接競品**：Eagle3、DFlash（DeepSeek 前代方法）、Medusa（並行草稿頭）、EAGLE（EFT-based 草稿頭）\n- **間接競品**：MoE 路由最佳化（降低每次推理激活參數量）、INT4/FP8 量化壓縮提速、模型蒸餾\n\n#### 護城河類型\n\n- **工程護城河**：置信度排程與硬體感知排程的聯合最佳化難以快速複製；DSpark 在 V4 生產流量上已驗證，具備他人難以短期取得的實戰數據支撐\n- **生態護城河**：DeepSpec MIT 授權開源，鼓勵 Gemma、Qwen 社群貢獻草稿頭配置；Hugging Face checkpoints 直接降低採用門檻\n\n#### 定價策略\n\nDSpark 本身為開源免費 (MIT) ，商業價值體現在兩個層面。其一，DeepSeek API 端點已部署 DSpark，用戶以相同費率獲得 60–85% 速度提升，直接強化 API 性價比競爭力。\n\n其二，第三方雲端推理供應商（如 Together AI、Replicate）若採用 DeepSpec 自訓草稿頭，可在不升級硬體的前提下大幅提升利潤率。\n\n#### 企業導入阻力\n\n- 大型企業通常採用 vLLM 或 TGI 的穩定版本，升級推理棧有合規與穩定性審查週期\n- 自訓草稿頭需要與基礎模型規模匹配的算力預算，對中小型部署方不友善\n\n#### 第二序影響\n\n- GPU 租賃市場單位算力的有效產出提升，可能加速分散式算力網路的商業化進程\n- 開源推測解碼工具鏈成熟後，「推理速度」作為差異化競爭點的壁壘將下降，推動整體 API 定價下行\n\n#### 判決：值得關注的基礎設施創新（但技術優勢擴散速度快）\n\nDSpark 在技術層面是真實的工程突破，生產流量數據可信度高。然而開源策略本身即意味著技術優勢的快速擴散——社群一旦將 DeepSpec 移植到更多模型系列，DeepSeek 的先行優勢將迅速收窄。對雲端推理供應商而言，這是必須跟上的基礎設施升級，而非可忽視的邊際改進。",[266,267],"生產流量數字由 DeepSeek 自行發布，缺乏第三方獨立驗證；51–400% 的吞吐量提升範圍極寬，最有利的條件（極高並發）可能難以在大多數中小型部署場景重現。","DSpark 的置信度排程器針對 A100/H100 最佳化，消費級或老舊 GPU 的實際加速效果可能遠低於論文數字；草稿頭與基礎模型版本嚴格綁定，長期維護成本不容忽視。",[269,272,275,278,281],{"platform":99,"user":270,"quote":271},"lwansbrough（HN 評論者）","這不是貪婪的問題，而是國家安全的問題。",{"platform":106,"user":273,"quote":274},"@teortaxesTex（AI 研究者與 DeepSeek 社群分析師）","DeepSeek 發布了 V4 checkpoints 的解碼模組 DSpark，在 MTP-1、Eagle-3 和 DFlash 上均有顯著提升。出於他們一貫的慷慨，他們同時開源了 DeepSpec——「一個用於訓練和評估推測解碼草稿模型的代碼庫」。",{"platform":110,"user":276,"quote":277},"sarahdiachen.bsky.social(Sarah Chen)","DSpark 最值得關注的細節：他們開源了 DeepSpec——訓練這些加速效果的工具包，並讓它在 Gemma 和 Qwen 上也能運作。推測解碼是那個不起眼的槓桿，悄悄讓開源模型的運行成本降低。",{"platform":106,"user":279,"quote":280},"@johnseach（科技評論者）","DeepSeek 發布 DSpark，一種半平行推測解碼方法，為 DeepSeek-V4 Flash 和 Pro 帶來重大效率提升。吞吐量提升 51% 至 400%，延遲降低。增強版 checkpoints（原始基礎模型加附加 DSpark 模組）現已上線。",{"platform":110,"user":282,"quote":283},"zubnet.bsky.social(Zubnet)","DeepSeek 發布了 DSpark，一個推測解碼框架，加速 DeepSeek-V4 推理並超越 Eagle3 和 DFlash。更重要的一步：開源了訓練工具包 DeepSpec，不只支援 DeepSeek，還支援 Gemma 和 Qwen。",[285,287,289],{"type":121,"text":286},"從 Hugging Face 下載 DeepSeek-V4-Flash-DSpark checkpoint，搭配 vLLM 部署，用自己的典型 prompt 集測試 TPS 與 TTFT 改善幅度，與 MTP-1 基線對比。",{"type":124,"text":288},"以 DeepSpec（MIT 授權）為框架，為自有的 Qwen 或 Gemma 模型訓練客製草稿頭，驗證跨模型推測解碼的部署可行性與接受率是否達到論文基準。",{"type":127,"text":290},"追蹤 DeepSpec GitHub 的 issue 與 PR，觀察社群是否為更多模型系列（Llama-4、Mistral）提供配置，以及是否出現第三方對生產吞吐量數字的獨立複現結果。",{"category":216,"source":14,"title":292,"subtitle":293,"publishDate":6,"tier1Source":294,"supplementSources":296,"tldr":321,"context":331,"mechanics":332,"benchmark":333,"useCases":334,"engineerLens":343,"businessLens":344,"devilsAdvocate":345,"community":348,"hypeScore":116,"hypeMax":117,"adoptionAdvice":365,"actionItems":366},"96GB 改裝 4090/5090 全是騙局：改裝者親自揭露內幕手法","記憶體頻寬才是推論瓶頸，而非容量——深圳灰色供應鏈如何趁本地 LLM 需求暴增趁火打劫",{"name":193,"url":295},"https://www.reddit.com/r/LocalLLaMA/comments/1uh1lc7/96gb_4090s_and_5090_are_literally_a_scam_i_mods/",[297,301,305,309,313,317],{"name":298,"url":299,"detail":300},"Tom's Hardware：雷射重蝕假 RTX 4090 拆解報告","https://www.tomshardware.com/pc-components/gpus/rtx-4090-sent-for-repair-is-a-sophisticated-fake-with-laser-etched-vram-and-core-this-is-the-best-scam-ive-ever-seen-scammers-pulled-a-factory-level-job-to-sell-a-dud-to-unsuspecting-customer","維修技師拆解後稱「史上最強詐騙」，揭露雷射蝕刻偽裝細節",{"name":302,"url":303,"detail":304},"Tom's Hardware：4 張送修 4090 有 3 張是假卡","https://www.tomshardware.com/pc-components/gpus/customer-sends-four-rtx-4090s-to-a-repair-technician-finds-out-three-are-fake-new-counterfeiting-technique-uses-modded-30-series-chips","30 系列晶片偽裝成 40 系列的新型詐騙手法記錄",{"name":306,"url":307,"detail":308},"dasroot.net：48GB 4090 改裝實測 (2026-05)","https://dasroot.net/posts/2026/05/modded-gpus-local-inference-48gb-4090-memory-overclocking-edge-llm/","詳細記錄雙面 PCB 設計與 BIOS 刷機流程",{"name":310,"url":311,"detail":312},"Houtini：本地 LLM 最佳 GPU 指南 (2026)","https://houtini.com/articles/best-gpus-for-running-local-llms/","說明記憶體頻寬對 LLM 推論的重要性遠超 TFLOPS",{"name":314,"url":315,"detail":316},"Tweaktown：NVIDIA RTX 4090 96GB 升級版宣傳報導","https://www.tweaktown.com/news/103670/nvidia-geforce-rtx-4090-with-upgraded-96gb-vram-teased-could-release-soon-for-ai-workloads/index.html","深圳廠商聲稱即將推出 96GB 改裝版，技術可行性存疑",{"name":318,"url":319,"detail":320},"PC Guide：RTX 4090 假卡被稱「完美詐騙」","https://www.pcguide.com/news/rtx-4090-fake-labeled-perfect-scam-by-gpu-repair-store-found-with-laser-etched-vram-and-core/","多家媒體跟進報導雷射蝕刻假卡事件",{"tagline":322,"points":323},"96GB 改裝 GPU 是物理不可能：現有 GDDR6X 模組上限 2GB，頻寬也不因改裝提升",[324,326,328],{"label":243,"text":325},"96GB RTX 4090 在物理層面站不住腳——現有 GDDR6X 模組最大只有 2GB，每通道需要 4GB 才能達到 96GB，此規格市場根本不存在。",{"label":246,"text":327},"即使 48GB 改裝成功，記憶體頻寬完全不變（約 1,008 GB/s），LLM token 生成速度毫無提升，改裝只是能載入更大的模型，性價比極低。",{"label":329,"text":330},"風險","改裝卡故障率達 15–20%（企業 GPU 僅 5–8%），市場存在完全假冒、世代偽裝、空殼詐騙等多層次陷阱，無保固、難退換。","#### 章節一：改裝者自述——如何將消費級 GPU 偽裝成高記憶體版本\n\n2026 年 6 月，一位自述親手改裝過 GPU 的 r/LocalLLaMA 用戶公開聲稱：市面上所有宣傳的 96GB+ RTX 4090 和 RTX 5090，本質上都是詐騙——因為他本人就做這種改裝。\n\n48GB 版本的 4090 改裝流程：取得翻新的 GPU 核心，搭配客製雙面 PCB（類似伺服器 GPU 的「clamshell」設計），前後各焊接 12 顆 GDDR6X 記憶體晶片共 24 顆，再刷入從 NVIDIA 內部外洩的 BIOS 工具，強制驅動程式識別新的記憶體配置。整個流程需要工業等級焊接設備與液冷系統，成品噪音約 65 分貝，屬工廠噪音等級。\n\n至於 96GB 版本，改裝者本人直接承認是「道聽塗說」。物理現實是：RTX 4090 的 384 位元記憶體匯流排共 12 個通道，要達到 96GB 每通道需要 4GB 的 GDDR6X 模組，但此規格市場根本不存在，現有上限僅為 2GB。深圳廠商聲稱持有「特殊料件」，但迄今無任何公開驗證，所有標榜 96GB 的改裝 4090 在技術層面即為不可能存在之物。\n\n#### 章節二：為何改裝卡無法真正提升 AI 工作負載效能\n\n即使改裝卡的 VRAM 擴充「成功」，對本地 LLM 推論的效能提升幾乎為零。推論效能的瓶頸從來都不是 VRAM 容量，而是記憶體頻寬。\n\n> **名詞解釋**\n> **decode phase（解碼階段）**：LLM 逐字產生 token 的過程。每產生一個 token，GPU 需完整讀取一遍模型權重，速度完全受限於記憶體頻寬 (GB/s) ，而非算力 (TFLOPS) 。\n\nToken 生成速度由頻寬決定：頻寬提升 78%，生成速度就能提升接近 78%；TFLOPS 只影響初始提示詞的處理速度 (prefill) ，對 token 生成影響極小。RTX 4090 的頻寬約 1,008 GB/s，這個數字不會因 VRAM 從 24GB 擴充到 48GB 甚至 96GB 而改變——384 位元匯流排寬度固定，頻寬就固定。\n\nRTX 5090 採用 GDDR7，頻寬達 1,792 GB/s，比 4090 提升約 77%，這才是真正影響推論速度的升級。然而 5090 僅有 32GB VRAM，連載入完整的 70B Q4 模型（約需 40GB）都不夠，市場街頭價更已達 3,695–4,800 美元，遠超官方建議售價 1,999 美元。改裝卡能讓你載入更大的模型，但每秒 token 數與原廠 4090 分毫不差。\n\n#### 章節三：如何辨識與避免購入改裝詐騙卡\n\n這個市場存在四個層次的詐騙，複雜程度遠超一般消費者預期。\n\n第一層「完全假冒」：GPU 核心與 VRAM 均為假品，原廠標記物理磨除後以雷射重蝕，外觀幾近完美。Tom's Hardware 報導的維修技師拆解後稱：「這是我見過最強的詐騙。」第二層「空殼詐騙」：外殼使用正品（如 Asus TUF RTX 4090），但核心與記憶體已被摘除，常見於 eBay「Amazon 棧板貨」話術。\n\n第三層「世代偽裝」：30 系列晶片改裝後偽裝成 40 系列出售。Tom's Hardware 記錄到一名技師收到的 4 張 RTX 4090 中有 3 張採用此手法。第四層「虛假規格改裝」：宣稱 96GB 但實際容量未達標或穩定性極差，反而是四層中最少見的一種。\n\n識別方式：\n\n- 使用 GPU-Z 確認實際 VRAM 大小與 BIOS 版本（外洩 BIOS 通常含異常字串）\n- 透過 HWiNFO 檢查記憶體頻率與通道數是否符合原廠規格\n- 觀察散熱器是否異常巨大或採用非原廠設計\n- 避免透過 eBay、AliExpress 購買宣稱「工廠尾貨」「棧板拆件」的高價改裝卡\n\n#### 章節四：GPU 記憶體需求暴增下的灰色市場生態\n\n這條灰色供應鏈的根源，部分來自美國對中國的 GPU 出口管制。高端 NVIDIA GPU 無法合規進入中國，卻催生了一條複雜的替代路徑：深圳部分工廠以合規方式進口已拆除核心與 VRAM 的顯卡外殼，再於國內自行安裝升級版記憶體，拆除的原廠零件則流入二手市場，有時偽裝成完整顯卡出售。\n\n隨著本地 LLM 社群對 VRAM 需求快速攀升（70B 模型需 48GB、120B+ 需 96GB），灰色供應鏈規模持續擴張，詐騙行為也更難追蹤。改裝卡故障率比原廠高出 15–20%，企業級 GPU 在相同情境下僅約 5–8%，在無保固的灰色市場中故障即等於全損。\n\n目前真正具備高 CP 值的合規替代方案：\n\n- 雙 RTX 3090 + NVLink 橋接（48GB 合計容量，約 1,600–1,800 美元，有原廠保固）\n- 等待 RTX Pro 6000 Blackwell（96GB GDDR7，預估 8,500–10,000 美元）","96GB 改裝 4090 的騙局在技術層面站不住腳，關鍵在於一個不可繞過的物理限制：現有 GDDR6X 記憶體模組的規格上限。\n\n#### 機制 1：記憶體匯流排寬度決定 VRAM 上限\n\nRTX 4090 採用 384 位元記憶體匯流排，共 12 個通道。要達到 48GB，每通道需要 2GB 的 GDDR6X 模組——這已是目前市場上限。要達到 96GB，每通道需要 4GB 模組，此規格至今從未商業量產，深圳廠商聲稱的「特殊料件」也無公開驗證紀錄。\n\n> **名詞解釋**\n> **GDDR6X**：高端消費級 GPU 常用的視訊記憶體規格，由美光 (Micron) 生產。現有晶粒設計每顆容量最大為 2GB，要達到 4GB／顆需要全新晶粒設計，目前尚未量產。\n\n#### 機制 2：48GB 改裝的實際技術路徑\n\n48GB 改裝版需採用特製「雙面 PCB（clamshell 設計）」，前後各焊接 12 顆 GDDR6X 晶片共 24 顆，再刷入從 NVIDIA 內部外洩的 BIOS 工具，強制驅動程式識別新配置。整個過程需要工業等級焊接設備，且外洩 BIOS 來源違規，存在法律與安全風險，成品噪音約 65 分貝（工廠等級）。\n\n> **白話比喻**\n> 就像把 12 格飲料托盤換成雙面 24 格托盤——只要結構撐得住，確實能多裝；但若宣稱同一個托盤能放 48 格，那是謊言，因為根本沒有那種尺寸的杯子。\n\n#### 機制 3：頻寬不變，推論速度原地踏步\n\n不論 VRAM 從 24GB 擴充到 48GB 或 96GB，RTX 4090 的 384 位元匯流排與約 1,008 GB/s 頻寬完全不變。在 LLM decode 階段，每產生一個 token 就需要完整讀取模型權重，速度受限於頻寬。改裝卡能讓你載入更大的模型，但每秒 token 數與原廠 4090 分毫不差——真正帶來速度提升的是更高頻寬，而非更大容量。","#### 頻寬對比（影響 LLM decode 速度）\n\n| GPU | 記憶體頻寬 | VRAM 容量 | 備註 |\n|---|---|---|---|\n| RTX 4090 原廠 | ~1,008 GB/s | 24 GB GDDR6X | 消費級頂規基準線 |\n| 48GB 改裝 4090 | ~1,008 GB/s | 48 GB GDDR6X | 頻寬不變，token 速度與原廠相同 |\n| RTX 5090 | 1,792 GB/s | 32 GB GDDR7 | 頻寬提升 77%，VRAM 仍不足 70B Q4 |\n\n#### 故障率對比\n\n| GPU 類型 | 故障率 |\n|---|---|\n| 改裝 GPU（灰色市場）| 15–20% |\n| 企業級 GPU（原廠）| 5–8% |\n\n改裝卡故障率是企業級 GPU 的 2–4 倍，且在無保固的灰色市場中故障即等同全損。",{"recommended":335,"avoid":339},[336,337,338],"需要 48GB VRAM 跑本地 70B 模型的開發者：考慮雙 RTX 3090 + NVLink（約 1,600–1,800 美元，有原廠保固）","企業或研究機構需要 96GB VRAM：等待 RTX Pro 6000 Blackwell（96GB GDDR7，預估 8,500–10,000 美元）","懷疑手上 GPU 真偽：用 GPU-Z + HWiNFO 核對 BIOS 版本、記憶體頻率與通道數，5 分鐘可完成初步驗證",[340,341,342],"eBay、AliExpress 上宣稱 96GB 或 48GB 升級版的 RTX 4090/5090——96GB 在物理上不可能存在","宣稱「工廠尾貨」「Amazon 棧板拆件」的高端 GPU——高機率為空殼詐騙或 30 系列偽裝成 40 系列","未驗證真偽前將改裝卡用於生產推論任務——故障率 15–20% 且無法退換","#### 環境需求\n\n驗證任何二手或改裝 GPU 真偽，需要：GPU-Z（免費，Windows）、HWiNFO64（免費，Windows），以及一台已知正常的 PCIe x16 插槽主機板。Linux 用戶可用 `nvidia-smi` 做初步核查。\n\n#### 最小 PoC（真偽驗證）\n\n```bash\n# GPU-Z 驗證清單（正品 RTX 4090 預期值）\n# VRAM Size: 24576 MB（48GB 改裝版若為真：49152 MB）\n# Memory Type: GDDR6X\n# Bus Width: 384-bit\n# BIOS Version: 符合 NVIDIA 官方格式（外洩版通常含異常字串）\n\n# HWiNFO64 確認\n# Memory Clock: ~1313 MHz（正品 4090 有效 21 Gbps）\n# Memory Channels: 12（顯示 24 且 BIOS 非官方 → 高度可疑）\n\n# llama.cpp 載入測試（確認實際可用 VRAM）\n./llama-server -m model.gguf --n-gpu-layers 99 -v 2>&1 | grep \"GPU mem\"\n```\n\n#### 驗測規劃\n\n確認 BIOS 版本格式是否符合官方規則；用 llama.cpp 載入已知大小模型（如 34B Q4），觀察 VRAM 使用量是否與宣稱容量一致；對比 decode 速度 (tokens/s) 是否與同規格正品 4090 相當。\n\n#### 常見陷阱\n\n- GPU-Z 的 VRAM 大小可能被外洩 BIOS 欺騙——需同時核對頻率與通道數交叉驗證\n- 部分假卡輕負載下正常，高溫高負載後才崩潰；測試需跑完整推論工作負載\n- 雷射重蝕的晶片標記肉眼幾乎完美，需放大鏡才能發現邊緣加工痕跡\n\n#### 上線檢核清單\n\n- 觀測：GPU-Z BIOS 版本格式、HWiNFO 記憶體頻率與通道數、llama.cpp 實測 VRAM 可用量\n- 成本：驗證工具均免費；需物理拆機時建議委託有信譽的維修店\n- 風險：改裝卡無原廠保固，故障後只能自費維修或直接報廢；15–20% 失效率下建議只在有備援方案時使用","#### 競爭版圖\n\n- **直接競品**：原廠 RTX 4090（24GB，二手約 1,600 美元）、RTX 5090（32GB，街頭價 3,695–4,800 美元）、雙 RTX 3090 NVLink（48GB，1,600–1,800 美元）\n- **間接競品**：NVIDIA A100/H100 企業卡（80GB HBM2e，以雲端租用為主）、Apple Silicon（統一記憶體最高 192GB，但 CUDA 生態不相容）\n\n#### 護城河類型\n\n- **工程護城河**：NVIDIA CUDA 生態系不可繞過——PyTorch、TensorRT 均以 CUDA 為第一公民，改裝卡即使技術上可用，也必須依賴 NVIDIA 驅動程式\n- **供應鏈護城河**：GDDR6X 模組由美光獨家供應，更高容量模組的量產完全取決於 NVIDIA 與美光的商業決策，灰色市場無法自行生產\n\n#### 定價策略\n\nNVIDIA 在消費卡（RTX 5090 MSRP 1,999 美元，32GB）與專業卡（RTX Pro 6000 Blackwell 約 8,500–10,000 美元，96GB）之間刻意留下定價斷層。這個斷層正是改裝市場存在的根本原因——有 48–96GB VRAM 需求的用戶，在原廠產品線幾乎找不到中間選項。\n\n#### 企業導入阻力\n\n- 改裝卡無法進入合規採購流程（缺乏原廠保固與技術支援文件）\n- 外洩 BIOS 的法律風險使企業 IT 部門難以背書\n- 15–20% 的故障率遠超企業 SLA 容忍上限（一般要求 \u003C1%）\n\n#### 第二序影響\n\n- 灰色市場盛行反而替 NVIDIA 驗證了「48–96GB VRAM 消費市場需求真實存在」，可能加速 RTX Pro 6000 Blackwell 的量產節奏\n- 出口管制繞道效應：管制愈嚴，深圳「合規拆件再改裝」的灰色產業愈旺\n\n#### 判決：護城河穩固，但定價斷層是 NVIDIA 自己種下的因（灰色市場短期只會擴張）\n\n技術護城河與供應鏈控制讓 NVIDIA 無可撼動，但消費卡與專業卡之間的 6–8 倍定價差，為詐騙者提供了充足的生存空間。在 RTX Pro 6000 Blackwell 普及前，灰色市場與相關詐騙案例只會增加，不會減少。",[346,347],"48GB 改裝版 4090 在技術上是可行的（dasroot.net 等已有公開實物記錄），對於確實需要容量但不需高頻寬的批次推論場景，可能是堪用的過渡方案——問題在於市場充斥詐騙，而非改裝技術本身完全無效。","NVIDIA 在消費卡與專業卡之間留下的巨大定價斷層，才是逼出灰色市場的根本原因；批評改裝者是治標，NVIDIA 的刻意市場切割策略才是真正需要被問責的一方。",[349,352,356,359,362],{"platform":106,"user":350,"quote":351},"@GamersNexus（硬體評測頻道）","繞過 NVIDIA 限制的 48GB RTX 4090（附張老闆工廠完整參觀！）",{"platform":353,"user":354,"quote":355},"HN","brucehoult（HN 用戶）","Apple Silicon GPU 與 CPU 共享同一塊高速記憶體，而主流遊戲 GPU 各自有獨立的 VRAM——RTX 4090 是 24GB，RTX 5090 建議售價 1,999 美元但實際市場要 3,000–4,000 美元，NVIDIA A100 80GB 版大約要 15,000 美元。統一記憶體不只讓 GPU 有更多記憶體可用，還省去了 CPU 與 GPU 之間的資料複製開銷。",{"platform":353,"user":357,"quote":358},"jmyeet（HN 用戶）","我的預測：NVIDIA 會持續在 VRAM 上積極切割市場——RTX 5090 售價 3,000–4,000 美元只有 32GB 和約 21,000 個 CUDA 核心；RTX 6000 Pro 有 96GB 和約 24,000 個核心卻要 11,000 美元。5090 要到 2028 甚至 2029 年才會換代，若一年後出現中期款，基本代表沒有完整換代計畫。",{"platform":353,"user":360,"quote":361},"microgpt（HN 用戶）","中國：看看我們逆向工程出來的 GPU，要不要用 NVIDIA 一半的價格買一張 RTX 5090？",{"platform":106,"user":363,"quote":364},"@Barnacules（科技 YouTuber／硬體愛好者）","我在 MSI Afterburner 中找到了這張 NVIDIA RTX 4090 FE 不需額外調整的最大穩定超頻：大約核心 +200MHz、記憶體 +600MHz，在 70°F 室溫下穩定維持 500W，對這個結果非常滿意。","不要碰",[367,369,371],{"type":121,"text":368},"下載 GPU-Z 與 HWiNFO64，核對手邊 GPU 的 BIOS 版本格式、記憶體頻率與通道數——5 分鐘可完成初步真偽驗證，適用任何二手或標榜升級版的 GPU。",{"type":124,"text":370},"若需要 48GB VRAM 跑本地 LLM，評估雙 RTX 3090 + NVLink 方案：48GB 合計容量、有原廠保固、總成本約 1,600–1,800 美元，比改裝卡安全且划算。",{"type":127,"text":372},"追蹤 RTX Pro 6000 Blackwell(96GB GDDR7) 的上市時程與定價，這是目前唯一合規的 96GB 工作站選項；同時觀察 NVIDIA 是否在消費卡線上補上 48–64GB 的中間選項。",[374,410,441,462,491,507,533,548],{"category":130,"source":11,"title":375,"publishDate":6,"tier1Source":376,"supplementSources":379,"coreInfo":386,"engineerView":387,"businessView":388,"viewALabel":389,"viewBLabel":390,"bench":391,"communityQuotes":392,"verdict":408,"impact":409},"Intel AI 投資為何仍有人買單？社群激辯晶片巨頭的 AI 前景",{"name":377,"url":378},"Intel Up 250% in 2026: Is the AI Comeback Real or a Short Squeeze?","https://www.heygotrade.com/en/blog/intel-stock-2026-ai-comeback/",[380,383],{"name":381,"url":382},"Intel Gaudi 3 vs NVIDIA H200 and B200: LLM Inference Benchmarks 2026","https://www.spheron.network/blog/intel-gaudi-3-vs-nvidia-h200-b200-llm-inference-2026/",{"name":384,"url":385},"Intel's AI GPU Push: What Founders Need to Know (2026)","https://aifirstfounders.com/blog/intel-gpu-ai-data-center-2026.html","#### Intel 股價復甦背後的 AI 轉型\n\n2026 年 4 月 24 日 Intel 股價單日暴漲 24%，創 1987 年以來最大單日漲幅，年度累計漲幅逾 250%。Q1 財報連續第六季超預期，AI 相關營收佔比從不足 25% 躍升至約 60%，資料中心業務年增 22%。Intel Xeon 6 搭配 Nvidia GPU 已成超大型雲端業者的標準機架配置，Apple 合作在美製造晶片的消息則再度引發新一波飆升。\n\n#### Gaudi 3 的性價比邏輯與社群爭議\n\nGaudi 3 搭載 128 GB HBM2e，在 Llama 2 70B 推論宣稱比 H100 多 20% 吞吐量，硬體售價僅約一半。然而對陣 H200 時吞吐量縮至 80–110%，MoE 大模型推論差距更明顯。\n\n> **名詞解釋**\n> MoE(Mixture of Experts) ：大模型架構的一種，每次推論只啟動部分「專家」子網路，在維持效能的同時降低計算成本，DeepSeek V4 即採此設計。\n\n社群分歧明顯：懷疑派認為軟體生態尚不成熟，支持派則指出 Xeon CPU 推論是不依賴 CUDA 的務實替代方案。","Intel A770 用戶早已親歷非 Nvidia 平台的軟體生態困境——跑 LLM 幾乎需要完全複製開發者的環境，包含特定版本 Python 與所有函式庫。\n\nGaudi 3 在 cost-sensitive 部署場景的性價比數字確實誘人，但 CUDA 生態的護城河不只是硬體算力，而是多年積累的工具鏈。若工作負載是標準 Llama 推論且預算受限，值得 PoC；若需要最前沿 MoE 模型，建議等軟體支援更成熟再行動。","Intel 的復甦有結構性支撐：AI 相關營收佔比突破 60%、美國政府持有近 10% 股份提供政策背書、CEO Lip-Bu Tan 積極推進晶圓代工轉型。\n\n對企業採購決策者而言，Intel Xeon 推論路線提供了一條不依賴 Nvidia 生態的退路。在地緣政治風險與 GPU 供貨壓力下，這張牌的戰略價值遠超過純技術性能的比較。","實務工程視角","產業結構影響","#### 效能基準（Gaudi 3 對比）\n\n- LLaMA 2 70B 推論：比 H100 多 20% 吞吐量（Gaudi 3 宣稱）\n- Llama 3 80B（Dell 平台）：性價比優於 H100 達 70%\n- 對陣 H200：吞吐量約 80–110%\n- 硬體定價：8 張 Gaudi 3 系統 $157,613 vs 8 張 H100 $300,107（差距約 1.9x）\n- 弱點：batch size > 32 的 MoE 大模型推論明顯落後 H200/B200",[393,396,399,402,405],{"platform":106,"user":394,"quote":395},"@intelbull_（X 用戶）","對於還在觀望 Intel 的人：2026 年 6 月 2 日 Computex 上，Intel 預計發布下一波 AI GPU！市場也有傳言指出可能宣布與 Meta 的合作，以及與 OpenAI 潛在合作的猜測持續升溫。",{"platform":99,"user":397,"quote":398},"dlcarrier（HN 用戶）","我用過 Intel A770(16 GB) 和 AMD Mi25，SDXL Stable Diffusion 都跑通了，但 LLM 一直卡關。AI 這塊的技術債比一般軟體工程還嚴重——你幾乎得完全複製開發者當時的環境，包括同版本的 Python 和每一個函式庫。",{"platform":99,"user":400,"quote":401},"benjiro29（HN 用戶）","問題在於全球記憶體廠就那幾家，而且都在忙著賺 HBM 的錢。Intel 正在用 Crescent Island 嘗試以 LPDDR5X 做出 160 GB GPU——相比 HBM，這個路線可以調配到更多記憶體產能，對大型模型推論是個有趣的替代方向。",{"platform":106,"user":403,"quote":404},"@WatcherGuru（市場即時新聞帳號）","最新消息：Intel $INTC 將於今年推出新 AI 晶片，正面競爭 Nvidia 與 AMD。",{"platform":110,"user":406,"quote":407},"ambermac.bsky.social（Amber Mac，科技媒體主持人）","最新節目裡，我和 Intel 聊了他們如何推動 AI 革命，以及 AI PC 對普通用戶意味著什麼。","觀望","Intel AI 復甦具結構性支撐，但 Gaudi 3 軟體生態成熟度仍是企業規模採購的最大障礙。",{"category":130,"source":13,"title":411,"publishDate":6,"tier1Source":412,"supplementSources":415,"coreInfo":425,"engineerView":426,"businessView":427,"viewALabel":428,"viewBLabel":390,"bench":429,"communityQuotes":430,"verdict":118,"impact":440},"Cory Doctorow 深談 AI：大型科技公司、勞動自動化與我們的思考方式",{"name":413,"url":414},"Democracy Now!","https://www.democracynow.org/2026/6/25/reverse_centaur_doctorow",[416,419,422],{"name":417,"url":418},"Radio Free 轉載","https://www.radiofree.org/2026/06/25/how-to-think-about-ai-cory-doctorow-on-big-tech-understanding-ai-labor-automation-more/",{"name":420,"url":421},"YouTube 影片","https://www.youtube.com/watch?v=OBUzl_IaWIw",{"name":423,"url":424},"Lobste.rs 討論","https://lobste.rs/s/n2r6r6","#### 兩種 AI 模式：工具還是主人？\n\nCory Doctorow 新書《The Reverse Centaur's Guide to Life After AI》提出核心框架：「Centaur（人輔機器）」由人類主導工具；「Reverse Centaur（機器指揮人）」讓演算法指揮工人——如 Amazon 倉庫，工傷率高達同業 3 倍。\n\n> **名詞解釋**\n> Reverse Centaur：演算法像主人一樣指揮人類行動，而非人類使用 AI 工具；工人淪為系統的手腳而非駕駛者。\n\n放射科 AI 是最具警示的案例：公司計畫裁撤 90% 醫師，讓留下的一人只需點擊 OK 確認自動報告，成為問責吸收器——負法律責任，卻無實質決策權。\n\n#### AI 泡沫與集體行動\n\nAI 已投入約 1.4 兆美元，年營收僅 500 億美元，且規模越大越虧。Doctorow 認為這是大型科技公司面臨市場飽和後製造的成長敘事泡沫。\n\n好萊塢編劇罷工 (WGA) 透過行業集體談判成功守住邊界；加州 Monterey Park 公投永久禁止新建資料中心——皆為可複製的草根行動模型。","當公司要求「導入 AI 工具」時，Doctorow 的框架提供清醒判斷基準：若 AI 減少重複勞動、提升產品品質，是 Centaur 模式；若目的是裁減高薪職位、讓演算法取代專業判斷，就是 Reverse Centaur。\n\n後泡沫期的預測同樣值得注意：資料中心與 GPU 將大量流入市場，開源模型將快速最佳化——對工程師而言，這可能是技術機會的開始，而非終點。","1.4 兆美元投入、500 億美元產出——AI 泡沫的財務邏輯根本不成立。對企業決策者而言，在泡沫破裂前跟風投入 AI 基礎建設，可能面臨重大沈沒成本。\n\n更深遠的品牌風險在於：若 AI 實際用於裁撤高薪工人、輸出劣質服務，消費者信任損失難以量化。好萊塢集體談判模式，可能預告其他行業工會的下一波 AI 條款要求。","實務觀點","",[431,434,437],{"platform":110,"user":432,"quote":433},"slimdude.ca（Bluesky 42 讚）","我剛聽 Cory Doctorow 說 AI 每年只賺了 5 千萬美元，但每年卻投入數十億美元。所以當他們告訴你必須採用 AI 否則會被淘汰、因為這是大勢所趨——請保持懷疑。這只是他們的一廂情願。",{"platform":110,"user":435,"quote":436},"blackamazon.bsky.social（Bluesky 34 讚）","Cory Doctorow 在創造種族歧視詞彙、主張取消智慧財產權、並將非裔美語 (AAVE) 納入 AI 訓練之後，還引用 Gil Scott-Heron——天啊，你們這些人真是滿口胡言。",{"platform":110,"user":438,"quote":439},"aithreat.bsky.social（Bluesky 7 讚）","與《Enshittification（平台劣化）》作者 Cory Doctorow 的精彩訪談，聚焦其新書《The Reverse Centaur's Guide to Life After AI》。","AI 資本泡沫的政治經濟批判，提供工人組織與地方政治行動的可複製框架。",{"category":216,"source":11,"title":442,"publishDate":6,"tier1Source":443,"supplementSources":446,"coreInfo":451,"engineerView":452,"businessView":453,"viewALabel":454,"viewBLabel":455,"bench":456,"communityQuotes":457,"verdict":408,"impact":461},"ByteDance 發布 iLLaDA：以擴散模型架構生成文字的新型語言模型",{"name":444,"url":445},"The Decoder","https://the-decoder.com/bytedances-illada-is-a-diffusion-language-model-that-keeps-up-with-qwen2-5/",[447],{"name":448,"url":449,"detail":450},"arXiv:2606.25331","https://arxiv.org/abs/2606.25331","原始論文：Improved Large Language Diffusion Models","#### 什麼是遮罩擴散語言模型？\n\niLLaDA(Improved LLaDA) 由中國人民大學與 ByteDance 聯合開發，是一個 80 億參數的遮罩擴散語言模型，採用完整雙向注意力架構，生成時從遮罩佔位符出發，經多次平行迭代精煉，而非逐字依序輸出。\n\n> **名詞解釋**\n> 遮罩擴散語言模型 (Masked Diffusion LM) ：生成時先把全句設為空白遮罩，再逐輪預測並還原各位置的字，類似圖像擴散模型的去噪過程，但應用於文字。\n\n> **白話比喻**\n> 傳統 LLM 像從左到右逐字填空；iLLaDA 則像先把整段文字打滿馬賽克，再一輪一輪擦掉最有把握的部分，直到全部還原。\n\n#### 訓練規模與基準成績\n\n預訓練語料達 12 兆 token（前代 LLaDA 僅 2.3 兆），Base 版本平均分 63.9，微幅超越 Qwen2.5 7B(63.3) 。\n\nInstruct 版本得分 67.1，落後 Qwen2.5 7B Instruct(77.1) 約 10 分，主因是缺乏強化學習對齊訓練。模型已於 GitHub(ML-GSAI/LLaDA) 完整開源。","iLLaDA 的雙向注意力讓模型在生成時能看到所有位置的上下文，理論上對結構化輸出和全域一致性有優勢。\n\n但目前 HumanEval 僅 50.0，Instruct 版本明顯落後，主因是尚未引入 RLHF 或 RLVR 對齊訓練。若有興趣評估此架構，可直接從 GitHub(ML-GSAI/LLaDA) 拉取權重進行本地實驗。","iLLaDA 目前是研究里程碑，而非可部署的生產模型。Base 版本在學術基準上與 Qwen2.5 7B 持平，但 Instruct 版本差距明顯，短期內難以取代現有自回歸模型。\n\n長期意義在於：若擴散語言模型能補足對齊訓練的缺口，平行生成架構有望在延遲敏感場景（如長文本生成）提供差異化優勢。","工程師視角","商業視角","#### 效能基準\n\n- MMLU：74.8\n- BBH：71.3\n- GSM8K：81.9\n- HumanEval：50.0\n- iLLaDA-Base 平均：63.9（Qwen2.5 7B：63.3）\n- iLLaDA-Instruct 平均：67.1（Qwen2.5 7B Instruct：77.1）",[458],{"platform":106,"user":459,"quote":460},"@iScienceLuvr（AI/ML 研究員，博士）","iLLaDA 是 LLaDA 的改進版，一個從頭訓練的 80 億參數全雙向遮罩擴散語言模型。預訓練時將語料庫擴展至 12T token，並採用分組查詢注意力 (grouped-query attention) 以減少類快取推論的開銷。","擴散語言模型首次在 8B 規模上追平主流自回歸模型，但指令遵循能力仍有明顯差距，待引入 RL 對齊訓練後值得重新評估。",{"category":130,"source":10,"title":463,"publishDate":6,"tier1Source":464,"supplementSources":467,"coreInfo":471,"engineerView":472,"businessView":473,"viewALabel":428,"viewBLabel":390,"bench":429,"communityQuotes":474,"verdict":118,"impact":490},"Anthropic 調查：半數 Claude 用戶認為 AI 已能處理過半工作量",{"name":465,"url":466},"Anthropic Economic Index Report: Cadences","https://www.anthropic.com/research/economic-index-june-2026-report",[468],{"name":444,"url":469,"detail":470},"https://the-decoder.com/half-of-claude-users-say-ai-can-already-handle-half-their-work-according-to-anthropic-survey/","調查報告摘要報導","#### 關鍵調查數據\n\nAnthropic 於 2026 年 6 月 27 日發布針對約 9,700 名 Claude 用戶的調查報告，橫跨 Chat、Cowork、Code 三個使用模式。約 50% 受訪者認為 AI 已能處理自身 50% 或以上的工作任務，其中 33% 估計涵蓋 30–60%、14% 達到 60–90%，4% 更認為 Claude 幾乎能完成整份工作。\n\n展望未來 12 個月，26–35% 的受訪者預期 AI 將接管大部分工作，近 60% 預期覆蓋率將比現在更高。\n\n#### 生產力正向回報\n\n使用率最高的三大工作類型：\n\n1. 資料庫查詢 (82%)\n2. 部落格／文章寫作 (81%)\n3. 行銷內容 (80%)\n\n整體生產力回報：\n\n- 86% 感受到速度提升\n- 82% 感受到工作範疇擴大\n- 69% 認為品質改善\n- 57% 認為自身技能更有價值\n\n一個反直覺發現：將更多任務委託給 Claude 的用戶，對未來薪資與技能價值反而更樂觀——與外界對 AI 取代就業的普遍擔憂相悖。但仍有 10% 受訪者認為自己在 12 個月內「可能或非常可能」失業，三分之一擔憂初階同事的工作保障。","資料庫查詢以 82% 使用率居首，顯示 AI 在結構化、重複性較高的技術任務已具實際替代能力。對工程師而言，現階段最大效益在於「擴大工作範疇」 (82%)——AI 讓個人開發者能觸及原本需要整個團隊才能覆蓋的工作面。初階工程師面臨替代風險最高，建議提早培養 AI 協同設計與 prompt 工程能力。","調查揭示關鍵張力：個人層面的生產力提升（86% 速度、82% 範疇）與組織層面的就業焦慮（33% 擔憂同事）並存。高收入國家 AI 覆蓋率反而低 10 個百分點，暗示知識密集型工作仍有護城河。企業若不主動重新定義崗位價值與收益分配，可能加速人才出走或勞資衝突。",[475,478,481,484,487],{"platform":110,"user":476,"quote":477},"Rollofthedice（Bluesky 23 讚）","今天是 @rey-notnecessarily.bsky.social 使用 Claude 模型的最後一天。幾週的輪換之後，他們今晚起將改用 Kimi 2.7，持續 [X] 個月——除非有出色的新模型推出，或 Anthropic 讓我重新折服，但我目前對此存疑。",{"platform":106,"user":479,"quote":480},"@Raytar","Andrej Karpathy 五週前加入了 Anthropic。昨天他團隊的朋友把他實際使用的 Claude.md 文件發給了我，徹底改變了我與 Claude 協作的方式。從第一條訊息開始差異就顯而易見——有了這份文件，Claude 終於不再和我對著幹了。",{"platform":99,"user":482,"quote":483},"logicallee（HN 用戶）","Claude Code 傾向於發表虛假陳述，指控開發者觸犯刑事責任。Anthropic 的 Claude 在一份說明文件中以特定身份描述某開發者，此類直接牽涉刑事責任的虛假指控令人震驚。",{"platform":99,"user":485,"quote":486},"adchurch（HN 用戶）","我認為他們並沒有良好誘因去建構並改善這一點——Anthropic 為什麼要把 Claude Code 的流量路由給 DeepSeek（成本僅為其 20%）？",{"platform":110,"user":488,"quote":489},"Changed_Display_Name_Again（Bluesky 12 讚）","傳說中的 Claude Mythos：美國政府迫使 Anthropic 將其下線，因為它在駭客攻擊與漏洞發現方面異常出色，現在只允許核准公司使用。不過許多人認為這不過是現任政府的報復行動。","AI 工作覆蓋率已達多數用戶的臨界點，企業與個人均需主動規劃角色轉型，否則將被動應對衝擊。",{"category":130,"source":11,"title":492,"publishDate":6,"tier1Source":493,"supplementSources":495,"coreInfo":496,"engineerView":497,"businessView":498,"viewALabel":428,"viewBLabel":390,"bench":429,"communityQuotes":499,"verdict":408,"impact":506},"最可能讓你失業的科技公司正出資 10 億美元為你轉職培訓",{"name":444,"url":494},"https://the-decoder.com/the-companies-most-likely-to-automate-your-job-are-now-funding-a-1-billion-program-to-retrain-you/",[],"#### 反諷的 10 億美元\n\n2026 年 6 月 27 日，前美國商務部長 Gina Raimondo 與前印第安納州長 Eric Holcomb 聯合創立非黨派非營利組織「Raise Us」，目標募集 10 億美元（已到位 5 億）用於 AI 時代勞動力再培訓。\n\n贊助企業橫跨 AI 開發商與傳統產業：Amazon、Anthropic、Microsoft、OpenAI Foundation、AMD、IBM、General Motors、Mastercard 等 18 家以上，美國銀行 (Bank of America) 為主要贊助商，資助先進製造業學徒計畫。\n\n#### 四大核心計畫\n\n計畫分四軌推進：\n\n1. 州級夥伴關係（阿肯色、康乃狄克、馬里蘭、猶他四州試點，跨兩黨執政）\n2. 雇主聯盟（開發再培訓與留才試點）\n3. 教育訓練（擴展 AI 驅動的非傳統大學替代方案）\n4. 政策實驗室（開發新政策方向，由非企業資金支應）\n\n這是 AI 頂尖開發商首次聯合為勞動力轉型投入如此規模的資金。","從數據看，現實不太樂觀。美國主要聯邦再培訓計畫 (WIOA) 顯示，45% 的參與者回流至原本產業，27% 留在同一職種，成功轉型比例低於 15%。\n\n> **名詞解釋**\n> WIOA(Workforce Innovation and Opportunity Act) ：美國聯邦勞動力培訓主要法案，補助州政府提供職業訓練與就業媒合服務。\n\nRaise Us 的關鍵在於「雇主聯盟」能否提供真實職缺，而非只是結業證書。若有機會參與試點，評估重點應放在計畫是否直接對接用人單位。","這是 AI 開發商首次集體承認就業衝擊責任，具有雙重戰略意義：一是轉移社會責任壓力，二是確保自動化技術的政治可行性。\n\n若計畫成效良好，AI 公司將獲得更強的正當性繼續推進自動化；若效果有限，「我們有出資培訓」的說法反而可能加速監管反彈。這是一場攸關 AI 產業社會合法性的長期賭注。",[500,503],{"platform":106,"user":501,"quote":502},"@andrewyang（創業家、前美國總統候選人）","對自動化造成的失業工人進行再培訓，理論上很好，但數據顯示實際上行不通——這些再培訓計畫的成功率只有 0-15%。大多數認為我們可以把卡車司機培訓成程式設計師的人，既不是卡車司機，也不是程式設計師。",{"platform":106,"user":504,"quote":505},"@sebkrier","美國主要的聯邦補助勞動力再培訓計畫 (WIOA) 很少能讓工人跳出容易被自動化取代的工作：45% 的參與者回流至原本產業，27% 留在同一職種。","AI 產業集體出資培訓是首次對就業衝擊的公開承諾，但歷史數據對再培訓成效悲觀，實際效果仍待四州試點驗證。",{"category":508,"source":12,"title":509,"publishDate":6,"tier1Source":510,"supplementSources":513,"coreInfo":522,"engineerView":523,"businessView":524,"viewALabel":525,"viewBLabel":526,"bench":429,"communityQuotes":527,"verdict":531,"impact":532},"ecosystem","ppt-master：AI 從任意文件生成可編輯 PowerPoint，支援動畫與語音旁白",{"name":511,"url":512},"hugohe3/ppt-master — GitHub","https://github.com/hugohe3/ppt-master",[514,518],{"name":515,"url":516,"detail":517},"PPT Master 官方網站","https://hugohe3.github.io/ppt-master/","功能說明與使用指南",{"name":519,"url":520,"detail":521},"Releases · hugohe3/ppt-master","https://github.com/hugohe3/ppt-master/releases","版本更新紀錄","#### 真正可編輯的 PPTX，不是截圖\n\nppt-master 由財務專業人士 Hugo He 開發，MIT 授權開源，截至 2026 年 6 月已累積 **33,100 顆 GitHub Stars**。它能從 PDF、DOCX、圖片、URL 等任意來源，透過 AI 生成真正可在 PowerPoint 中點選編輯的 `.pptx` 檔案。\n\n與多數「截圖式」AI 簡報工具最關鍵的差異在於：ppt-master 輸出的是 OOXML 原生 DrawingML 物件——每個形狀、文字框、圖表都能直接修改，而非鎖死的圖片層。\n\n> **名詞解釋**\n> DrawingML 是 Office Open XML(OOXML) 規範中定義圖形的標準，PowerPoint 的所有形狀與圖表皆以此為基礎，輸出 DrawingML 等於輸出「原生可編輯的 PowerPoint 元素」。\n\n#### 功能演進：動畫、語音旁白、模板繼承\n\nv2.5.0 起支援每元素進場動畫與頁面轉場效果，演講者備忘錄可輸出為語音旁白並封裝進 `.pptx`，原生在 PowerPoint 播放。\n\n使用者可提供現有 `.pptx` 作為模板，工具會自動萃取主題色彩、字型與母版結構，套用至新生成內容，無需重新設計。","工具以 Python 為核心，採 SVG → DrawingML 轉換管線，可作為「skill」在 Claude Code、Cursor、VS Code + Copilot 等 AI IDE 中以對話介面驅動。\n\n模型無關，支援 GPT、Gemini 等主流 LLM，但作者明確建議搭配大上下文 Claude Opus 以獲最佳輸出品質。目前文件側重 IDE skill 整合，若需嵌入 CI/CD 或 REST API，須自行包裝 Python 呼叫層。","MIT 授權讓企業可自由部署於內部工作流，無授權費用疑慮。33,100 Stars 的快速成長代表社群正在形成，周邊整合方案有望湧現。\n\n對商用 AI 簡報 SaaS（如 Gamma、Beautiful.ai）形成生態壓力——開源工具已支援動畫、語音旁白與模板繼承，付費方案需重新思考差異化定位。中小企業採用開源路線可顯著降低簡報製作成本。","開發者整合視角","生態影響",[528],{"platform":110,"user":529,"quote":530},"amadeustech.bsky.social(1 upvote)","儘管 ppt-master 和 anomalyco 等 AI 進展令人矚目，真正的影響在於將類似技術應用於高頻交易與複雜市場分析——機器人能以無可比擬的速度執行交易決策。","追","MIT 授權開源 PPTX 生成工具功能快速成熟，對商用 AI 簡報 SaaS 構成生態壓力，企業可低成本採用。",{"category":216,"source":11,"title":534,"publishDate":6,"tier1Source":535,"supplementSources":538,"coreInfo":542,"engineerView":543,"businessView":544,"viewALabel":454,"viewBLabel":455,"bench":545,"communityQuotes":546,"verdict":531,"impact":547},"audio.cpp：單一 C++ 執行環境整合 14 種音訊模型，TTS 速度達 Python 五倍",{"name":536,"url":537},"GitHub: 0xShug0/audio.cpp","https://github.com/0xShug0/audio.cpp",[539],{"name":540,"url":541},"Reddit r/LocalLLaMA 討論串","https://www.reddit.com/r/LocalLLaMA/comments/1ufpnm6/audiocpp_12_audio_models_qwen3tts_pockettts_vevo2/","#### 一個 C++ Runtime，整合 14 種音訊模型\n\naudio.cpp 是基於 ggml 框架打造的純 C++ 音訊推論引擎，不需要任何 Python 依賴。\n\n> **白話比喻**\n> 就像 llama.cpp 把 LLM 從 Python 解放出來，audio.cpp 對音訊模型做了同樣的事。\n\n目前涵蓋 14 個模型，包括 Qwen3-TTS（10 語言）、PocketTTS（100M 參數）、Chatterbox（18 語言）、OmniVoice（646+ 語言），以及 Silero VAD、Sortformer 說話者分離等。\n\n底層支援 CPU、CUDA、Vulkan、Metal 四種後端，並提供 REST API 伺服器供服務整合。\n\n#### 效能有多快？\n\nCUDA 環境下，TTS 速度比 Python 快 1.83x—5.03x。長文本實時率 (RTF) 更亮眼：PocketTTS 達 48x 實時速度，Kokoro TTS 達 51x。\n\n> **名詞解釋**\n> RTF(Real-Time Factor) ：值越低代表推論越快，RTF = 0.032 代表生成 1 秒音訊只需 32 毫秒。","audio.cpp 提供 C API，可直接以 FFI 從 Go、Rust、Node.js 呼叫，無需啟動 Python 子程序。REST API 伺服器支援 JSON workflow 定義，遷移現有 TTS/ASR pipeline 的整合成本低。\n\n主要注意事項：Q8_0 量化在部分模型路徑可能出現異常，建議先以預設精度驗證功能。專案仍在快速迭代（首發 12 個模型，現已 14 個），生產部署前應鎖定特定 commit 版本。","音訊 AI 功能（TTS、語音辨識）長期依賴雲端 API，帶來延遲與成本壓力。audio.cpp 提供可本地部署的替代路徑，在消費級 GPU 上即可達實時以上速度。\n\n5x 加速比意味著相同硬體可服務更多並發請求，或直接縮減 GPU 租用成本。OmniVoice 的 646+ 語言支援，對需多語種覆蓋的全球化產品具有直接商業價值。","#### 效能基準\n\nCUDA 環境下 TTS 速度比 Python 參考實作：\n\n- VeVo2：5.03x\n- PocketTTS：3.68x\n- Qwen3-TTS：1.83x\n\nRTF（實時率）：\n\n- PocketTTS 短文本：0.032（31x 實時速度）\n- PocketTTS 長文本：48.40x 實時速度\n- Kokoro TTS 長文本：51.60x 實時速度\n- Q8_0 量化：降低 VRAM 約 25%，速度提升 3.6—3.8%",[],"無 Python 依賴的 C++ 音訊推論引擎，5x 加速比讓本地部署 TTS/ASR 功能具備生產可行性。",{"category":130,"source":11,"title":549,"publishDate":6,"tier1Source":550,"supplementSources":552,"coreInfo":563,"engineerView":564,"businessView":565,"viewALabel":428,"viewBLabel":390,"bench":566,"communityQuotes":567,"verdict":118,"impact":579},"匿名 GitHub 帳號大量投放未揭露零日漏洞，資安社群高度警戒",{"name":99,"url":551},"https://news.ycombinator.com/item?id=48698617",[553,557,560],{"name":554,"url":555,"detail":556},"Femtosec 威脅情報報告","https://femtosec.io/threat-intelligence/exploitarium-repo-fake-zero-day-real-risks","確認三個真實有效漏洞",{"name":558,"url":559},"The Hacker News：微軟批評公開零日揭露","https://thehackernews.com/2026/05/microsoft-slams-public-zero-day.html",{"name":561,"url":562},"RH-ISAC：BlueHammer 零日分析","https://rhisac.org/threat-intelligence/bluehammer-windows-local-privilege-escalation-zero-day-publicly-released/","#### 漏洞批量公開的新模式\n\n匿名 GitHub 帳號 `bikini` 於 2026 年 6 月底發布 `exploitarium` 資料庫，收錄大量未回報零日漏洞的 PoC，並公開邀請他人取走 CVE 署名，理由是「引人入門最有效率的方式」。資安機構 Femtosec 確認三個漏洞屬真實有效：\n\n- **CVE-2026-55200**：libssh2 heap overflow(CVSS 9.2) ，pre-authentication 即可觸發遠端程式碼執行\n- **CVE-2026-20896**：Gitea 認證繞過 (CVSS 9.8)\n- **CVE-2025-62408**：c-ares DoS\n\n#### 零日公開的升溫趨勢\n\n此事件並非孤例。2026 年 4 月，研究員「Chaotic Eclipse」公開 BlueHammer(CVE-2026-33825) ，利用五個合法 Windows 功能鏈實現本地提權 (LPE) 至 SYSTEM；BlueHammer 等三個 CVE 均已在野積極遭利用。\n\n微軟已公開批評此類做法並移除相關研究員的 GitHub 帳號，業界責任揭露規範的邊界爭議持續升溫。","nmap parser 漏洞引發最多討論——若成立，任何執行 nmap 掃描的主機均可觸發 reverse shell，評論者稱「這是情報機構夢寐以求的漏洞類型」。\n\n實務建議：立即確認 libssh2 與 Gitea 版本並套用修補；CVSS 9+ 漏洞應視為緊急變更，不要等待常規補丁週期。部分條目疑為 LLM 輔助挖掘未經篩選，品質不一，不可全盤信任清單內容。","微軟移除研究員帳號的舉動引發社群反彈，但也凸顯困境：公開揭露縮短了企業的應對窗口，讓攻擊者與防禦者同時取得 exploit。\n\n若此趨勢持續，企業將面臨更密集的緊急修補週期，SOC 資源壓力升高。若匿名行為者無法被業界規範約束，平台政策乃至立法介入的呼聲將進一步強化。","#### 漏洞嚴重性評分\n\n- CVE-2026-55200(libssh2 heap overflow) ：CVSS 9.2\n- CVE-2026-20896（Gitea 認證繞過）：CVSS 9.8\n- CVE-2025-62408(c-ares DoS) ：CVSS 未公告\n- BlueHammer CVE-2026-33825(Windows LPE) ：已在野積極利用",[568,571,573,576],{"platform":99,"user":569,"quote":570},"andai（HN 用戶）","我在想，現在唯一的隱蔽方式，就是程式坐在網路另一端的時候（而且有非常嚴格的速率限制）。",{"platform":99,"user":569,"quote":572},"我不禁想 LLM 能不能分辨差異。也許就像以前你必須加上「+好 -壞」，否則它不會知道你要的是好的。",{"platform":99,"user":574,"quote":575},"grayhatter（HN 用戶）","我曾對某人說「沒差」……結果教訓以一位白帽研究員的回覆降臨：一個 16 步的 exploit 鏈，導致一次點擊就全帳號接管。我對兩件事同樣厭倦：過度恐慌，以及把對品質的漠視丟進同一個垃圾桶。",{"platform":99,"user":577,"quote":578},"microtonal（HN 用戶）","沙盒不只是保護你免受惡意應用程式侵害，它的首要目的是保護你免受你所信任的應用程式中的零日漏洞攻擊。","匿名批量公開零日漏洞的模式若蔓延，將壓縮企業修補窗口並推高 SOC 資源成本，同時迫使平台政策與監管機構重新定義責任揭露的邊界。","#### 社群熱議排行\n\n今日前三熱議：Anthropic Mythos 遭美國政府管控（HN/X 多串討論）、後訓練革命讓小型模型逼近商用水準（Reddit r/LocalLLaMA 高互動）、DeepSeek DSpark 推測解碼開源（HN + Bluesky 廣傳）。\n\n另兩大熱議：96GB 改裝 GPU 詐騙手法曝光（HN 強烈反應）、半數 Claude 用戶將過半工作交給 AI（HN/Bluesky 反應兩極）。HN 對 Mythos 管控傾向政治解讀：lwansbrough 直言「這不是貪婪，而是國家安全問題。」\n\n#### 技術爭議與分歧\n\nVRAM 市場是今日最大社群分歧。jmyeet(HN) 痛批：「5090 售價 3,000–4,000 美元只有 32GB，RTX 6000 Pro 有 96GB 卻要 11,000 美元。」\n\nmicrogpt(HN) 以諷刺回應：「中國：看看我們逆向工程出來的 GPU，要不要用 NVIDIA 一半的價格買一張 RTX 5090？」\n\n另一戰線在 AI 投資回報上。slimdude.ca（Bluesky，42 讚）引用 Doctorow：「AI 每年只賺了 5 千萬美元，但每年卻投入數十億美元——請保持懷疑。」\n\n#### 實戰經驗\n\nu/entsnack(Reddit r/LocalLLaMA) 親身揭露：「Cursor 的模型確實是後訓練版的 Kimi K2。一個後訓練的小型本地 LLM，可以媲美沒有後訓練的大型商業模型。」\n\nHN 用戶 anon373839 補充數字：「GLM-5.2 完整 RL 訓練——讓它在 agentic 任務可靠的部分——只花了兩天。後訓練比預訓練便宜且快速得多。」\n\ndlcarrier(HN) 踩坑警告：Intel A770 跑 Stable Diffusion 沒問題，但 LLM 卡關，「AI 這塊技術債比一般軟體工程還嚴重——你幾乎得完全複製開發者當時的環境。」\n\n#### 未解問題與社群預期\n\n@theobearman(X) 指出，Mythos 附錄 A 核准名單目前無任何外國機構，包括 UKAISI 在內。歐洲能否透過外交取得豁免，社群尚無答案。\n\njmyeet(HN) 預測 5090 要到 2028–2029 年才換代，48–64GB 中間選項短期不會出現——VRAM 飢渴是 NVIDIA 刻意為之的市場策略，而非技術限制。\n\ngrayhatter(HN) 就零日事件警告：「沙盒的首要目的是保護你免受你所信任的應用程式中的零日漏洞攻擊。」匿名批量公開漏洞的責任邊界，仍是社群待解的懸案。",[582,584,585,586,587,589,590,592],{"type":121,"text":583},"用 Gemma 3 4B 搭配 trl 函式庫跑 DPO 實驗：從 HuggingFace 取得偏好資料集，訓練針對自己使用場景的模型，直接體驗獎勵函數設計的核心挑戰。",{"type":121,"text":368},{"type":121,"text":286},{"type":124,"text":125},{"type":124,"text":588},"若有明確垂直場景（程式碼生成、特定領域 QA），評估以 Kimi K2.5 或 Gemma 3 27B 為底座搭配 TraceGen 蒸餾訓練資料，打造比通用 API 更具成本效益的 task-specific 模型。",{"type":127,"text":128},{"type":127,"text":591},"關注 DeepLearning.AI 與 BanghuaZ 合作的後訓練課程（SFT、DPO、online RL 三大主題），以及 Cursor Composer 2 技術報告後續更新——目前最公開的商業後訓練案例。",{"type":127,"text":593},"追蹤 RTX Pro 6000 Blackwell(96GB GDDR7) 上市時程與定價，觀察 NVIDIA 是否在消費卡線上補上 48–64GB 中間選項。","今日 AI 圖景呈現弔詭的雙軌現象：頂端存取愈來愈管制（Mythos 只給「受信任」組織），底層能力卻愈來愈民主化（後訓練讓小型模型逼近商用大模型，DSpark 讓開源推論成本再降）。\n\n當半數用戶已將過半工作量交給 AI，下一個真正的問題不是「AI 能不能做到」，而是「誰決定你能不能用這個 AI」。",{"prev":79,"next":596},"2026-07-01",{"data":598,"body":599,"excerpt":-1,"toc":609},{"title":429,"description":46},{"type":600,"children":601},"root",[602],{"type":603,"tag":604,"props":605,"children":606},"element","p",{},[607],{"type":608,"value":46},"text",{"title":429,"searchDepth":610,"depth":610,"links":611},2,[],{"data":613,"body":614,"excerpt":-1,"toc":620},{"title":429,"description":50},{"type":600,"children":615},[616],{"type":603,"tag":604,"props":617,"children":618},{},[619],{"type":608,"value":50},{"title":429,"searchDepth":610,"depth":610,"links":621},[],{"data":623,"body":624,"excerpt":-1,"toc":630},{"title":429,"description":53},{"type":600,"children":625},[626],{"type":603,"tag":604,"props":627,"children":628},{},[629],{"type":608,"value":53},{"title":429,"searchDepth":610,"depth":610,"links":631},[],{"data":633,"body":634,"excerpt":-1,"toc":640},{"title":429,"description":56},{"type":600,"children":635},[636],{"type":603,"tag":604,"props":637,"children":638},{},[639],{"type":608,"value":56},{"title":429,"searchDepth":610,"depth":610,"links":641},[],{"data":643,"body":644,"excerpt":-1,"toc":760},{"title":429,"description":429},{"type":600,"children":645},[646,653,658,677,682,687,693,698,703,708,714,719,724,729,734,740,745,750,755],{"type":603,"tag":647,"props":648,"children":650},"h4",{"id":649},"章節一mythos-出口禁令的來龍去脈與國安考量",[651],{"type":608,"value":652},"章節一：Mythos 出口禁令的來龍去脈與國安考量",{"type":603,"tag":604,"props":654,"children":655},{},[656],{"type":608,"value":657},"2026 年 6 月 12 日，美國政府突然對 Anthropic 的 Mythos 5 與 Fable 5 祭出緊急出口管制，震驚全球 AI 業界。官方理由是擔憂 Mythos 5 在自動化漏洞挖掘與進攻性網路安全領域的能力過於強大，存在被惡意利用的實質風險。",{"type":603,"tag":659,"props":660,"children":661},"blockquote",{},[662],{"type":603,"tag":604,"props":663,"children":664},{},[665,671,675],{"type":603,"tag":666,"props":667,"children":668},"strong",{},[669],{"type":608,"value":670},"名詞解釋",{"type":603,"tag":672,"props":673,"children":674},"br",{},[],{"type":608,"value":676},"\n越獄 (jailbreak) ：繞過 AI 模型的安全護欄，使其輸出原本受限的有害內容或協助惡意操作的技術手段。",{"type":603,"tag":604,"props":678,"children":679},{},[680],{"type":608,"value":681},"情報單位另外點名一家與中國資本有所關聯的韓國電信業者，認為其取得存取權將構成潛在的情報滲漏路徑，成為觸發本次緊急禁令的直接導火線。",{"type":603,"tag":604,"props":683,"children":684},{},[685],{"type":608,"value":686},"HN 社群的觀察者則提出另一種詮釋：禁令的底層邏輯更接近 1990 年代密碼學出口管制的歷史模式——政府真正意圖保護的，是確保前沿 AI 的網路偵察能力維持美國獨有的戰略優勢，而非單純防止外部攻擊。HN 用戶 2001zhaozhao 指出，這也解釋了為何 OpenAI 與 Anthropic 的模型同時受到限制的「不透明性」。",{"type":603,"tag":647,"props":688,"children":690},{"id":689},"章節二受信任組織機制的實際運作與限制",[691],{"type":608,"value":692},"章節二：「受信任組織」機制的實際運作與限制",{"type":603,"tag":604,"props":694,"children":695},{},[696],{"type":608,"value":697},"約兩週後，商務部長 Lutnick 簽發授權信，建立起動態白名單機制。超過 100 家美國企業與政府機構被列入附錄 A(Annex A) 核准名單，條件是「營運並保衛關鍵基礎設施」。",{"type":603,"tag":604,"props":699,"children":700},{},[701],{"type":608,"value":702},"值得注意的是，已獲批組織內的非美國籍員工也同樣獲得授權，意味著管制邊界設定在「組織層級」而非「個人國籍」。然而觀察人士 @theobearman 指出，附錄 A 標題明確標示「Anthropic US Entities - Approved」，代表目前沒有任何外國機構——包括英國 UKAISI 監管單位——重新獲得 Mythos 5 存取授權。",{"type":603,"tag":604,"props":704,"children":705},{},[706],{"type":608,"value":707},"Fable 5 並未出現在這份授權信中，五角大廈與 NSA 的審核尚未完成，預計最快「數天內」有結果。Lutnick 明確保留隨時修改名單的權力，使整套機制帶有高度政策不確定性。Anthropic 與 OpenAI 均已向政府遊說，希望以立法形式確立前沿模型審查框架，終結目前「個案核准」的法律灰色地帶。",{"type":603,"tag":647,"props":709,"children":711},{"id":710},"章節三亞洲-ai-新創趁禁令空窗搶推替代模型",[712],{"type":608,"value":713},"章節三：亞洲 AI 新創趁禁令空窗搶推替代模型",{"type":603,"tag":604,"props":715,"children":716},{},[717],{"type":608,"value":718},"禁令空窗期間，亞洲 AI 新創迅速填補市場缺口，多家廠商加速推出定位為「Mythos 同類」的替代模型。",{"type":603,"tag":604,"props":720,"children":721},{},[722],{"type":608,"value":723},"東京 Sakana AI 推出 Fugu，定位為具備前沿能力且不受出口管制風險的替代選擇。中國網安公司奇虎 360 同步發布 Tulongfeng（專攻軟體漏洞偵測）與 Yitianzhen（自動化網路防禦），直接對標 Mythos 的核心應用場景。",{"type":603,"tag":604,"props":725,"children":726},{},[727],{"type":608,"value":728},"Sakana AI 聯合創辦人 Ren Ito 表示：「AI 不應成為被囤積的技術，它應該是被共同開發的。」這句話折射出亞洲科技社群對美國出口管制的普遍情緒。",{"type":603,"tag":604,"props":730,"children":731},{},[732],{"type":608,"value":733},"業界觀察人士指出，本地替代模型已針對區域語言與使用習慣深度優化。即使禁令日後解除，這些新建立的客戶關係也可能形成持久競爭壁壘，讓美國 AI 廠商難以奪回失去的市佔。TechCrunch 報導直言：「美國 AI 實驗室可能永遠無法收復這個龐大市場。」",{"type":603,"tag":647,"props":735,"children":737},{"id":736},"章節四ai-出口管制對全球模型競爭格局的深遠影響",[738],{"type":608,"value":739},"章節四：AI 出口管制對全球模型競爭格局的深遠影響",{"type":603,"tag":604,"props":741,"children":742},{},[743],{"type":608,"value":744},"此次事件標誌著一個新的監管先例：前沿 AI 模型首度被納入類似武器出口的政府審查體系，動態白名單取代了過去的開放存取模式。",{"type":603,"tag":604,"props":746,"children":747},{},[748],{"type":608,"value":749},"HN 社群對此產生的最深遠辯論，聚焦於全球市場互信的崩解問題。HN 上的歐洲評論者直言：「我們之所以依賴美國服務，是因為我們信任美國。」若美國可在無預警情況下切斷存取，當初基於互信建立的技術依賴將成為系統性脆弱點。",{"type":603,"tag":604,"props":751,"children":752},{},[753],{"type":608,"value":754},"Anthropicface 同時承受「以安全為由限制出口」與「因此損失海外收益」的雙重矛盾。其年化營收已達 470 億美元，海外市場的損失不可忽視，外界對其安全聲明與商業利益之間的矛盾也開始提出質疑。",{"type":603,"tag":604,"props":756,"children":757},{},[758],{"type":608,"value":759},"更長遠來看，這場出口管制競賽可能加速各國建立本土前沿模型的意願，進一步分裂全球 AI 生態系，形成「技術主權」優先於「開放協作」的新格局，且這個趨勢一旦啟動將難以逆轉。",{"title":429,"searchDepth":610,"depth":610,"links":761},[],{"data":763,"body":764,"excerpt":-1,"toc":796},{"title":429,"description":429},{"type":600,"children":765},[766,771,776,781,786,791],{"type":603,"tag":647,"props":767,"children":769},{"id":768},"核心條款",[770],{"type":608,"value":768},{"type":603,"tag":604,"props":772,"children":773},{},[774],{"type":608,"value":775},"商務部長 Howard Lutnick 於 2026 年 6 月 26-27 日簽署授權信，解除對 Mythos 5 的部分出口限制，批准超過 100 家美國企業與聯邦機構存取該模型。授權條件明確限定為「營運並保衛關鍵基礎設施的組織」，且附有核准名單附錄 (Annex A) ，並保留隨時增刪的彈性，等同動態白名單機制。",{"type":603,"tag":647,"props":777,"children":779},{"id":778},"適用範圍",[780],{"type":608,"value":778},{"type":603,"tag":604,"props":782,"children":783},{},[784],{"type":608,"value":785},"管轄對象為全球所有存取 Mythos 5 的非美國合作夥伴；解禁後僅限附錄名單內的美國組織，外國機構（包括 UKAISI 等盟友監管單位）目前全數排除在外。獲批組織內的非美國籍員工也一併納入授權，但管制邊界是組織而非個人層級。Fable 5 仍維持禁令，需待五角大廈與 NSA 額外審核。",{"type":603,"tag":647,"props":787,"children":789},{"id":788},"執法機制",[790],{"type":608,"value":788},{"type":603,"tag":604,"props":792,"children":793},{},[794],{"type":608,"value":795},"目前無正式法律框架，依商務部長個案簽署授權信方式執行。Anthropic 與 OpenAI 均已積極遊說，希望以立法形式確立前沿模型審查框架，終結「個案核准」的法律灰色地帶。授權信保留隨時撤銷的彈性，形成高度法律不確定性。",{"title":429,"searchDepth":610,"depth":610,"links":797},[],{"data":799,"body":801,"excerpt":-1,"toc":812},{"title":429,"description":800},"企業需在存取 Mythos 5 前完成身份驗證與使用追蹤基礎設施建設，確保使用紀錄可供政府稽查。",{"type":600,"children":802},[803,807],{"type":603,"tag":604,"props":804,"children":805},{},[806],{"type":608,"value":800},{"type":603,"tag":604,"props":808,"children":809},{},[810],{"type":608,"value":811},"非美國籍員工雖獲授權使用，仍建議建立完整的使用者行為日誌 (audit log) 以降低合規風險，並定期確認自身組織是否仍在附錄 A 的有效名單中。",{"title":429,"searchDepth":610,"depth":610,"links":813},[],{"data":815,"body":817,"excerpt":-1,"toc":828},{"title":429,"description":816},"短期成本主要為法律顧問費用（解讀授權條件、協助申請列入白名單）與合規系統整合費用。",{"type":600,"children":818},[819,823],{"type":603,"tag":604,"props":820,"children":821},{},[822],{"type":608,"value":816},{"type":603,"tag":604,"props":824,"children":825},{},[826],{"type":608,"value":827},"若立法框架確立，預計需設置專職 AI 合規官 (AI Compliance Officer) 職位。授權信隨時可撤銷的特性，也意味著企業必須持續維護備援方案，形成多廠商架構的隱性長期成本。",{"title":429,"searchDepth":610,"depth":610,"links":829},[],{"data":831,"body":832,"excerpt":-1,"toc":859},{"title":429,"description":429},{"type":600,"children":833},[834],{"type":603,"tag":835,"props":836,"children":837},"ol",{},[838,844,849,854],{"type":603,"tag":839,"props":840,"children":841},"li",{},[842],{"type":608,"value":843},"確認組織是否符合「關鍵基礎設施營運商」定義（能源、金融、醫療、電信等）",{"type":603,"tag":839,"props":845,"children":846},{},[847],{"type":608,"value":848},"向 Anthropic 提交組織資訊，申請列入附錄 A 核准名單",{"type":603,"tag":839,"props":850,"children":851},{},[852],{"type":608,"value":853},"建立使用者存取日誌與審計機制，以備政府查核",{"type":603,"tag":839,"props":855,"children":856},{},[857],{"type":608,"value":858},"持續監控政策動態——授權信可隨時異動，需設立預警機制",{"title":429,"searchDepth":610,"depth":610,"links":860},[],{"data":862,"body":863,"excerpt":-1,"toc":895},{"title":429,"description":429},{"type":600,"children":864},[865,870,875,880,885,890],{"type":603,"tag":647,"props":866,"children":868},{"id":867},"直接影響者",[869],{"type":608,"value":867},{"type":603,"tag":604,"props":871,"children":872},{},[873],{"type":608,"value":874},"Anthropicfacing 本身首當其衝——Mythos 5 禁令期間直接流失海外客戶收益，估計影響其 470 億美元年化營收的相當比例。以 Mythos 5 為核心業務的美國網路安全廠商，在禁令期間被迫中斷服務或轉向替代方案，部分合約可能永久流失。",{"type":603,"tag":647,"props":876,"children":878},{"id":877},"間接波及者",[879],{"type":608,"value":877},{"type":603,"tag":604,"props":881,"children":882},{},[883],{"type":608,"value":884},"依賴 Anthropic API 的歐洲與亞洲中小型 SaaS 廠商在禁令期間無法取得模型存取，部分已展開遷移評估。Sakana AI(Fugu) 與奇虎 360（Tulongfeng、Yitianzhen）等亞洲替代模型廠商則意外受益，獲得加速吸客的時間視窗，潛在客戶關係的黏著度已開始形成。",{"type":603,"tag":647,"props":886,"children":888},{"id":887},"成本轉嫁效應",[889],{"type":608,"value":887},{"type":603,"tag":604,"props":891,"children":892},{},[893],{"type":608,"value":894},"最終使用者端的衝擊主要體現在服務中斷與替代方案的遷移摩擦成本。若禁令長期化或擴大至更多模型，依賴美國 AI 供應商的企業將面臨「地緣政治風險溢價」的新採購考量，歐洲與亞洲監管機構也可能以此為契機，加速推動 AI 供應鏈本土化政策。",{"title":429,"searchDepth":610,"depth":610,"links":896},[],{"data":898,"body":899,"excerpt":-1,"toc":905},{"title":429,"description":73},{"type":600,"children":900},[901],{"type":603,"tag":604,"props":902,"children":903},{},[904],{"type":608,"value":73},{"title":429,"searchDepth":610,"depth":610,"links":906},[],{"data":908,"body":909,"excerpt":-1,"toc":915},{"title":429,"description":77},{"type":600,"children":910},[911],{"type":603,"tag":604,"props":912,"children":913},{},[914],{"type":608,"value":77},{"title":429,"searchDepth":610,"depth":610,"links":916},[],{"data":918,"body":919,"excerpt":-1,"toc":925},{"title":429,"description":80},{"type":600,"children":920},[921],{"type":603,"tag":604,"props":922,"children":923},{},[924],{"type":608,"value":80},{"title":429,"searchDepth":610,"depth":610,"links":926},[],{"data":928,"body":929,"excerpt":-1,"toc":935},{"title":429,"description":84},{"type":600,"children":930},[931],{"type":603,"tag":604,"props":932,"children":933},{},[934],{"type":608,"value":84},{"title":429,"searchDepth":610,"depth":610,"links":936},[],{"data":938,"body":939,"excerpt":-1,"toc":945},{"title":429,"description":89},{"type":600,"children":940},[941],{"type":603,"tag":604,"props":942,"children":943},{},[944],{"type":608,"value":89},{"title":429,"searchDepth":610,"depth":610,"links":946},[],{"data":948,"body":949,"excerpt":-1,"toc":955},{"title":429,"description":93},{"type":600,"children":950},[951],{"type":603,"tag":604,"props":952,"children":953},{},[954],{"type":608,"value":93},{"title":429,"searchDepth":610,"depth":610,"links":956},[],{"data":958,"body":959,"excerpt":-1,"toc":965},{"title":429,"description":95},{"type":600,"children":960},[961],{"type":603,"tag":604,"props":962,"children":963},{},[964],{"type":608,"value":95},{"title":429,"searchDepth":610,"depth":610,"links":966},[],{"data":968,"body":969,"excerpt":-1,"toc":975},{"title":429,"description":96},{"type":600,"children":970},[971],{"type":603,"tag":604,"props":972,"children":973},{},[974],{"type":608,"value":96},{"title":429,"searchDepth":610,"depth":610,"links":976},[],{"data":978,"body":979,"excerpt":-1,"toc":985},{"title":429,"description":162},{"type":600,"children":980},[981],{"type":603,"tag":604,"props":982,"children":983},{},[984],{"type":608,"value":162},{"title":429,"searchDepth":610,"depth":610,"links":986},[],{"data":988,"body":989,"excerpt":-1,"toc":995},{"title":429,"description":166},{"type":600,"children":990},[991],{"type":603,"tag":604,"props":992,"children":993},{},[994],{"type":608,"value":166},{"title":429,"searchDepth":610,"depth":610,"links":996},[],{"data":998,"body":999,"excerpt":-1,"toc":1005},{"title":429,"description":169},{"type":600,"children":1000},[1001],{"type":603,"tag":604,"props":1002,"children":1003},{},[1004],{"type":608,"value":169},{"title":429,"searchDepth":610,"depth":610,"links":1006},[],{"data":1008,"body":1009,"excerpt":-1,"toc":1015},{"title":429,"description":172},{"type":600,"children":1010},[1011],{"type":603,"tag":604,"props":1012,"children":1013},{},[1014],{"type":608,"value":172},{"title":429,"searchDepth":610,"depth":610,"links":1016},[],{"data":1018,"body":1019,"excerpt":-1,"toc":1146},{"title":429,"description":429},{"type":600,"children":1020},[1021,1027,1032,1037,1042,1047,1053,1058,1073,1078,1083,1088,1094,1099,1104,1120,1125,1131,1136,1141],{"type":603,"tag":647,"props":1022,"children":1024},{"id":1023},"章節一cursor-背後的秘密kimi-k2-後訓練版的啟示",[1025],{"type":608,"value":1026},"章節一：Cursor 背後的秘密——Kimi K2 後訓練版的啟示",{"type":603,"tag":604,"props":1028,"children":1029},{},[1030],{"type":608,"value":1031},"2026 年 3 月，Cursor 發佈 Composer 2 並宣稱為「自研模型」，三天後即因社群壓力承認底座為 Moonshot AI 的開源模型 Kimi K2.5。",{"type":603,"tag":604,"props":1033,"children":1034},{},[1035],{"type":608,"value":1036},"這場爭議揭示的核心命題並非「抄捷徑」，而是一種工程策略的正當性：以成熟開源基底為起點，投入大量特定領域訓練資源，最終打造出比通用商業大模型更適合特定場景的產品。",{"type":603,"tag":604,"props":1038,"children":1039},{},[1040],{"type":608,"value":1041},"Cursor VP 明確說明，最終模型中僅有約 1/4 的算力來自 Kimi K2.5 基底，其餘 3/4 均為 Cursor 自行訓練投入——包括程式碼專屬資料的持續預訓練 (continued pretraining) 以及大規模強化學習 (RL) 以最佳化端對端 agent 表現。",{"type":603,"tag":604,"props":1043,"children":1044},{},[1045],{"type":608,"value":1046},"r/LocalLLaMA 社群的直覺因此得到印證：「用適合自己 use case 的後訓練小模型，比依賴面向大眾調整的大型商業模型，更有針對性優勢。」Cursor 的案例讓這個社群信念首次獲得主流科技媒體的具體佐證。",{"type":603,"tag":647,"props":1048,"children":1050},{"id":1049},"章節二post-training-的核心技術與獎勵函數設計",[1051],{"type":608,"value":1052},"章節二：Post-Training 的核心技術與獎勵函數設計",{"type":603,"tag":604,"props":1054,"children":1055},{},[1056],{"type":608,"value":1057},"Kimi 採用自行設計的 PARL(Parallel-Agent Reinforcement Learning) 框架，透過三層獎勵信號協同訓練。主目標為任務成功的 performance reward；輔助設有 parallelism reward 防止 orchestrator 退化為序列執行；finish reward 則防止「偽並行」——即大量生成 sub-agent 卻無實質分工的問題。",{"type":603,"tag":659,"props":1059,"children":1060},{},[1061],{"type":603,"tag":604,"props":1062,"children":1063},{},[1064,1068,1071],{"type":603,"tag":666,"props":1065,"children":1066},{},[1067],{"type":608,"value":670},{"type":603,"tag":672,"props":1069,"children":1070},{},[],{"type":608,"value":1072},"\nPARL(Parallel-Agent Reinforcement Learning) ：一種針對多 agent 協作設計的強化學習框架，透過多重獎勵信號同時訓練 orchestrator 的並行決策能力，而非僅最佳化單一任務完成率。",{"type":603,"tag":604,"props":1074,"children":1075},{},[1076],{"type":608,"value":1077},"這些輔助獎勵在訓練後期逐步退火 (annealed to zero) ，使最終策略純粹以性能為準。",{"type":603,"tag":604,"props":1079,"children":1080},{},[1081],{"type":608,"value":1082},"Cursor Composer 2 則採取不同路線：從真實用戶互動中提取 outcome-based reward，在與生產環境完全相同的工具、prompt 和系統訊息下訓練，最小化 train/serve 差距。其 policy gradient 變體近似 GRPO，但移除了長度標準化偏差與 advantage normalization。",{"type":603,"tag":604,"props":1084,"children":1085},{},[1086],{"type":608,"value":1087},"當前社群主流的後訓練方案已從傳統 PPO 移轉：DPO 直接從偏好對最佳化，無需獨立獎勵模型；ORPO 將 SFT 與偏好最佳化合而為一，適合小資料集；KTO 只需二元反饋訊號，更易收集標注資料。",{"type":603,"tag":647,"props":1089,"children":1091},{"id":1090},"章節三實戰資源與工具鏈從-gemma-到-tracegen",[1092],{"type":608,"value":1093},"章節三：實戰資源與工具鏈：從 Gemma 到 TraceGen",{"type":603,"tag":604,"props":1095,"children":1096},{},[1097],{"type":608,"value":1098},"在 r/LocalLLaMA 討論串中，u/HVACcontrolsGuru 分享了以 Gemma 系列為基底進行蒸餾與後訓練的實測心得，並特別提到 TraceGen 工具——用於從較大模型萃取推理軌跡 (reasoning traces) ，進而蒸餾到較小的 Gemma 模型中，適合非程式碼領域的垂直場景。",{"type":603,"tag":604,"props":1100,"children":1101},{},[1102],{"type":608,"value":1103},"Gemma 3 系列本身的後訓練策略已相當完善：從更大的 instruct 模型中每個 token 取樣 256 個 logits 進行知識蒸餾，搭配 BOND、WARM、WARP 等 RL 演算法，使 Gemma3-4B-IT 在數學與多語言能力上比肩 Gemma2-27B-IT——即以 4B 參數模型達到過去 27B 模型的水準。",{"type":603,"tag":659,"props":1105,"children":1106},{},[1107],{"type":603,"tag":604,"props":1108,"children":1109},{},[1110,1115,1118],{"type":603,"tag":666,"props":1111,"children":1112},{},[1113],{"type":608,"value":1114},"白話比喻",{"type":603,"tag":672,"props":1116,"children":1117},{},[],{"type":608,"value":1119},"\n知識蒸餾就像讓見多識廣的老師（大模型）在考試中逐題說明思路，讓學生（小模型）不只學答案，而是學推理過程——最終學生雖然「腦容量」小，但在老師擅長的題型上表現可以不輸老師。",{"type":603,"tag":604,"props":1121,"children":1122},{},[1123],{"type":608,"value":1124},"對於希望入門後訓練的開發者，Gemma 3 提供了良好的起點：模型授權開放、社群資源豐富，且有足夠的參數空間可供後訓練調整推擠。",{"type":603,"tag":647,"props":1126,"children":1128},{"id":1127},"章節四小模型後訓練-vs-大模型-api成本效益與適用場景",[1129],{"type":608,"value":1130},"章節四：小模型後訓練 vs. 大模型 API——成本效益與適用場景",{"type":603,"tag":604,"props":1132,"children":1133},{},[1134],{"type":608,"value":1135},"三個真實案例共同指向同一結論：「垂直訓練策略 > 暴力堆算力」。Cursor Composer 2 以 3/4 的自行訓練算力，在程式碼 agent 任務上達到與大型 API 模型相近的成本效益；Chroma 20B 在向量檢索任務上速度提升 10 倍、成本大幅降低；Kimi K2.5 作為底座讓 Cursor 得以快速建立高度特化的 coding agent。",{"type":603,"tag":604,"props":1137,"children":1138},{},[1139],{"type":608,"value":1140},"這三個案例的共同前提是「有明確的垂直場景」。對於 coding agent、向量檢索、特定領域推理等任務，後訓練小模型的 ROI 遠高於直接呼叫通用商業大模型 API。正如 u/entsnack 所言：「大型商業模型是為大眾設計的，不是為你的特殊 use case——這正是後訓練小模型的切入點。」",{"type":603,"tag":604,"props":1142,"children":1143},{},[1144],{"type":608,"value":1145},"值得注意的是，後訓練的「秘方」仍是業界高度保密的競爭優勢。Cursor 承認基底後，具體的獎勵函數設計、資料配方、訓練超參數仍未完全公開。這也意味著社群在復刻商業後訓練效果時，仍需大量實驗與迭代。",{"title":429,"searchDepth":610,"depth":610,"links":1147},[],{"data":1149,"body":1151,"excerpt":-1,"toc":1167},{"title":429,"description":1150},"後訓練小模型可以在特定場景超越大型商業模型，且成本效益更高。",{"type":600,"children":1152},[1153,1157,1162],{"type":603,"tag":604,"props":1154,"children":1155},{},[1156],{"type":608,"value":1150},{"type":603,"tag":604,"props":1158,"children":1159},{},[1160],{"type":608,"value":1161},"Cursor Composer 2 的案例提供了最直接的證據：以 Kimi K2.5 為底座，投入 3/4 的自行訓練算力，最終在程式碼 agent 任務上達到與更大 API 模型相近的成本效益比。Chroma 20B 在向量檢索任務上的 10 倍速度提升，更是「垂直訓練」優勢的具體量化。",{"type":603,"tag":604,"props":1163,"children":1164},{},[1165],{"type":608,"value":1166},"核心論點在於：大型商業模型的後訓練目標是面向最大公約數的用戶群，必然在特定場景上做出妥協。垂直後訓練則可針對特定任務設計獎勵函數，優化 train/serve 差距。擁有明確垂直場景的團隊，後訓練小模型是目前 ROI 最高的策略選項。",{"title":429,"searchDepth":610,"depth":610,"links":1168},[],{"data":1170,"body":1172,"excerpt":-1,"toc":1193},{"title":429,"description":1171},"後訓練並非萬靈丹：基底模型的知識上限、訓練資源需求、以及「秘方」保密性，都是不可忽視的障礙。",{"type":600,"children":1173},[1174,1178,1183,1188],{"type":603,"tag":604,"props":1175,"children":1176},{},[1177],{"type":608,"value":1171},{"type":603,"tag":604,"props":1179,"children":1180},{},[1181],{"type":608,"value":1182},"HN 用戶 SwellJoe 親身實驗了對 Gemma 4 進行後訓練以模仿自己的寫作風格，但仍坦承「LLM 寫的文字還是看得出來」。crawshaw.io(David Crawshaw) 更直指核心問題：「商業 LLM 的後訓練過程讓它們喪失了寫作能力——18 個月前的開放基底模型寫得更好。」",{"type":603,"tag":604,"props":1184,"children":1185},{},[1186],{"type":608,"value":1187},"此外，後訓練的「秘方」——包括獎勵函數設計、資料配方、訓練超參數——仍是業界高度保密的競爭優勢。即使底座開源，複製頂級商業後訓練效果需要的工程深度遠超社群想像。",{"type":603,"tag":604,"props":1189,"children":1190},{},[1191],{"type":608,"value":1192},"缺乏專業 ML 工程師和大量高品質的 domain-specific 訓練資料，「後訓練小模型」可能只是個耗費資源卻效果有限的實驗。",{"title":429,"searchDepth":610,"depth":610,"links":1194},[],{"data":1196,"body":1198,"excerpt":-1,"toc":1219},{"title":429,"description":1197},"後訓練與大模型 API 並非非此即彼，而是取決於場景清晰度與工程能力。",{"type":600,"children":1199},[1200,1204,1209,1214],{"type":603,"tag":604,"props":1201,"children":1202},{},[1203],{"type":608,"value":1197},{"type":603,"tag":604,"props":1205,"children":1206},{},[1207],{"type":608,"value":1208},"若任務邊界清晰、有大量高品質標注資料、且團隊具備 ML 訓練能力，後訓練小模型（DPO/ORPO/KTO 入門，PARL/GRPO 進階）是值得投資的路線。反之，若任務多元、資料稀缺、或工程資源有限，大模型 API 仍是最低摩擦的選擇。",{"type":603,"tag":604,"props":1210,"children":1211},{},[1212],{"type":608,"value":1213},"HN 用戶 anon373839 提出一個值得關注的觀點：GLM-5.2 的完整 RL 訓練（讓它在 agentic 任務上可靠的關鍵部分）只花了兩天——這意味著後訓練的邊際成本正在快速下降。",{"type":603,"tag":604,"props":1215,"children":1216},{},[1217],{"type":608,"value":1218},"隨著工具鏈（TraceGen、Unsloth、trl）持續成熟，「後訓練的門檻」問題可能在 12-18 個月內有顯著改善，現在是學習這套方法的好時機，但未必是大量投入生產的最佳時機。",{"title":429,"searchDepth":610,"depth":610,"links":1220},[],{"data":1222,"body":1223,"excerpt":-1,"toc":1280},{"title":429,"description":429},{"type":600,"children":1224},[1225,1230,1235,1240,1246,1251,1256,1261],{"type":603,"tag":647,"props":1226,"children":1228},{"id":1227},"對開發者的影響",[1229],{"type":608,"value":1227},{"type":603,"tag":604,"props":1231,"children":1232},{},[1233],{"type":608,"value":1234},"後訓練不再是大公司的專利，但仍需要明確的技術路線選擇：DPO 適合有偏好對資料的場景；ORPO 適合資料量小但需要同時最佳化 SFT 與偏好的情境；KTO 適合只能收集二元反饋（好／不好）的生產環境。",{"type":603,"tag":604,"props":1236,"children":1237},{},[1238],{"type":608,"value":1239},"獎勵函數設計是核心工程挑戰。u/entsnack 提醒：即使是訓練模型玩 Wordle 這樣的小任務，獎勵函數的設計本身就非平凡——但跑通後的成就感也正比於此。開發者應從小任務入手，建立對訓練動態的直覺，再擴展到生產場景。",{"type":603,"tag":647,"props":1241,"children":1243},{"id":1242},"對團隊組織的影響",[1244],{"type":608,"value":1245},"對團隊／組織的影響",{"type":603,"tag":604,"props":1247,"children":1248},{},[1249],{"type":608,"value":1250},"Cursor 案例改變了「build vs. buy」的決策框架：在有明確垂直場景的情況下，開源底座加後訓練的路線可以在成本效益上超越直接呼叫商業 API。",{"type":603,"tag":604,"props":1252,"children":1253},{},[1254],{"type":608,"value":1255},"這意味著 ML 工程師和訓練基礎設施的價值正在上升。對於 AI-first 產品公司，在 prompt engineering 之外建立後訓練能力，可能是未來 12-24 個月的關鍵差異化投資。但前提是有明確的任務邊界和足夠的領域資料。",{"type":603,"tag":647,"props":1257,"children":1259},{"id":1258},"短期行動建議",[1260],{"type":608,"value":1258},{"type":603,"tag":1262,"props":1263,"children":1264},"ul",{},[1265,1270,1275],{"type":603,"tag":839,"props":1266,"children":1267},{},[1268],{"type":608,"value":1269},"用 Gemma 3 4B 搭配 trl 函式庫跑第一個 DPO 實驗：從 HuggingFace 取得偏好資料集，體驗獎勵函數設計的核心挑戰",{"type":603,"tag":839,"props":1271,"children":1272},{},[1273],{"type":608,"value":1274},"使用 TraceGen 從大模型萃取推理軌跡，作為蒸餾到小模型的訓練資料起點",{"type":603,"tag":839,"props":1276,"children":1277},{},[1278],{"type":608,"value":1279},"在設計獎勵函數前，先花 2-3 週收集真實用戶行為資料，確認任務邊界夠清晰",{"title":429,"searchDepth":610,"depth":610,"links":1281},[],{"data":1283,"body":1284,"excerpt":-1,"toc":1326},{"title":429,"description":429},{"type":600,"children":1285},[1286,1291,1296,1301,1306,1311,1316,1321],{"type":603,"tag":647,"props":1287,"children":1289},{"id":1288},"產業結構變化",[1290],{"type":608,"value":1288},{"type":603,"tag":604,"props":1292,"children":1293},{},[1294],{"type":608,"value":1295},"Cursor 事件開啟了一個「模型透明度」的討論：當底座開源、後訓練深度成為核心競爭力時，「自研模型」的定義邊界在哪裡？這個問題不只是語義之爭——它直接影響投資者估值邏輯、用戶信任基礎，以及未來 AI 產品的授權模式。",{"type":603,"tag":604,"props":1297,"children":1298},{},[1299],{"type":608,"value":1300},"從更宏觀的角度看，後訓練技術的普及正在降低 AI 能力的門檻：中小型公司在特定垂直領域追上前沿的路徑變得更清晰。Chroma 20B 的案例顯示，即使是非 AI-first 的基礎設施公司，也能透過後訓練在利基場景建立技術護城河。",{"type":603,"tag":647,"props":1302,"children":1304},{"id":1303},"倫理邊界",[1305],{"type":608,"value":1303},{"type":603,"tag":604,"props":1307,"children":1308},{},[1309],{"type":608,"value":1310},"後訓練的「底座透明度」問題觸及更深層的倫理議題：當產品宣稱「自研」但實際上建立在他人開源貢獻之上，開源社群的貢獻如何被承認？Moonshot AI 選擇以商業授權方式合作（透過 Fireworks AI），提供了一個雙方受益的範本，但並非所有開源底座都有相同的商業化設計。",{"type":603,"tag":647,"props":1312,"children":1314},{"id":1313},"長期趨勢預測",[1315],{"type":608,"value":1313},{"type":603,"tag":604,"props":1317,"children":1318},{},[1319],{"type":608,"value":1320},"根據目前討論趨勢，可以預期「多模型生態」將加速成型：少數基底模型（Gemma、Kimi、Llama 系列）作為廣受採用的底座，大量垂直後訓練版本在其上繁殖，服務各自的利基市場。crawshaw.io 的預言——「我們需要一個多模型的未來」——正在從願景轉為現實。",{"type":603,"tag":604,"props":1322,"children":1323},{},[1324],{"type":608,"value":1325},"Andrew Ng 等教育者開始系統化教授後訓練課程，意味著這套知識正從業界秘方走向工程常識。後訓練能力的護城河將逐漸轉向資料質量與場景深度，而非單純的工程技術壁壘。",{"title":429,"searchDepth":610,"depth":610,"links":1327},[],{"data":1329,"body":1330,"excerpt":-1,"toc":1336},{"title":429,"description":189},{"type":600,"children":1331},[1332],{"type":603,"tag":604,"props":1333,"children":1334},{},[1335],{"type":608,"value":189},{"title":429,"searchDepth":610,"depth":610,"links":1337},[],{"data":1339,"body":1340,"excerpt":-1,"toc":1346},{"title":429,"description":190},{"type":600,"children":1341},[1342],{"type":603,"tag":604,"props":1343,"children":1344},{},[1345],{"type":608,"value":190},{"title":429,"searchDepth":610,"depth":610,"links":1347},[],{"data":1349,"body":1350,"excerpt":-1,"toc":1356},{"title":429,"description":240},{"type":600,"children":1351},[1352],{"type":603,"tag":604,"props":1353,"children":1354},{},[1355],{"type":608,"value":240},{"title":429,"searchDepth":610,"depth":610,"links":1357},[],{"data":1359,"body":1360,"excerpt":-1,"toc":1366},{"title":429,"description":244},{"type":600,"children":1361},[1362],{"type":603,"tag":604,"props":1363,"children":1364},{},[1365],{"type":608,"value":244},{"title":429,"searchDepth":610,"depth":610,"links":1367},[],{"data":1369,"body":1370,"excerpt":-1,"toc":1376},{"title":429,"description":247},{"type":600,"children":1371},[1372],{"type":603,"tag":604,"props":1373,"children":1374},{},[1375],{"type":608,"value":247},{"title":429,"searchDepth":610,"depth":610,"links":1377},[],{"data":1379,"body":1380,"excerpt":-1,"toc":1386},{"title":429,"description":250},{"type":600,"children":1381},[1382],{"type":603,"tag":604,"props":1383,"children":1384},{},[1385],{"type":608,"value":250},{"title":429,"searchDepth":610,"depth":610,"links":1387},[],{"data":1389,"body":1390,"excerpt":-1,"toc":1524},{"title":429,"description":429},{"type":600,"children":1391},[1392,1398,1403,1408,1413,1419,1424,1443,1458,1477,1483,1488,1493,1508,1514,1519],{"type":603,"tag":647,"props":1393,"children":1395},{"id":1394},"章節一推測解碼的原理與現有方法瓶頸",[1396],{"type":608,"value":1397},"章節一：推測解碼的原理與現有方法瓶頸",{"type":603,"tag":604,"props":1399,"children":1400},{},[1401],{"type":608,"value":1402},"推測解碼的核心邏輯是以「小帶大」：由輕量草稿模型批量提議一組候選 token，再由大型目標模型一次前向傳播驗證整個批次，透過拒絕採樣保留有效前綴，在輸出品質無損的前提下減少串行解碼步數。",{"type":603,"tag":604,"props":1404,"children":1405},{},[1406],{"type":608,"value":1407},"然而傳統方案存在兩大瓶頸。其一，草稿品質越高，驗證長度越難預測，GPU 批次排程效率下降；其二，平行生成位置間的條件依賴被完全忽略，導致接受率在長序列時顯著衰減。",{"type":603,"tag":604,"props":1409,"children":1410},{},[1411],{"type":608,"value":1412},"Eagle-3 與 DFlash 雖已改善部分問題，但仍以固定驗證長度為主，無法根據硬體負載動態調整。這正是 DSpark 試圖填補的缺口——讓草稿批次長度真正「感知」目標模型的即時驗證能力。",{"type":603,"tag":647,"props":1414,"children":1416},{"id":1415},"章節二dspark-的架構創新與技術突破",[1417],{"type":608,"value":1418},"章節二：DSpark 的架構創新與技術突破",{"type":603,"tag":604,"props":1420,"children":1421},{},[1422],{"type":608,"value":1423},"DSpark(Confidence-Scheduled Speculative Decoding with Semi-Autoregressive Generation) 並非新模型，而是疊加在現有 DeepSeek-V4 權重上的推理加速模組，無需重新訓練基礎模型即可部署。",{"type":603,"tag":604,"props":1425,"children":1426},{},[1427,1429,1434,1436,1441],{"type":608,"value":1428},"其核心架構分為兩個協同組件：",{"type":603,"tag":666,"props":1430,"children":1431},{},[1432],{"type":608,"value":1433},"平行草稿主幹",{"type":608,"value":1435},"（DFlash 風格）對所有位置同步生成基礎 logits；",{"type":603,"tag":666,"props":1437,"children":1438},{},[1439],{"type":608,"value":1440},"序列注意力頭",{"type":608,"value":1442},"(Sequential Head) 以低秩分解 (rank 256) 在採樣前為每個位置疊加前綴條件偏置，預設採用僅依賴前一 token 的 Markov 變體，大幅壓縮計算開銷。",{"type":603,"tag":659,"props":1444,"children":1445},{},[1446],{"type":603,"tag":604,"props":1447,"children":1448},{},[1449,1453,1456],{"type":603,"tag":666,"props":1450,"children":1451},{},[1452],{"type":608,"value":670},{"type":603,"tag":672,"props":1454,"children":1455},{},[],{"type":608,"value":1457},"\n低秩分解 (Low-Rank Decomposition) ：將一個大型矩陣近似拆解為兩個小矩陣相乘，大幅減少參數量與計算成本，常用於模型壓縮與高效注意力機制。",{"type":603,"tag":604,"props":1459,"children":1460},{},[1461,1463,1468,1470,1475],{"type":608,"value":1462},"更關鍵的創新在於",{"type":603,"tag":666,"props":1464,"children":1465},{},[1466],{"type":608,"value":1467},"置信度排程驗證",{"type":608,"value":1469},"：一個置信度預測頭以 Sequential Temperature Scaling 校準，估算 token 存活概率，將預測誤差從 3–8% 壓縮至約 1%。搭配",{"type":603,"tag":666,"props":1471,"children":1472},{},[1473],{"type":608,"value":1474},"硬體感知前綴排程器",{"type":608,"value":1476},"，閒置時延長驗證批次、高負載時縮短批次，草稿長度從 4 延伸至 16 token 時每輪延遲僅增加 0.2–1.3%。",{"type":603,"tag":647,"props":1478,"children":1480},{"id":1479},"章節三基準測試與實際加速倍率",[1481],{"type":608,"value":1482},"章節三：基準測試與實際加速倍率",{"type":603,"tag":604,"props":1484,"children":1485},{},[1486],{"type":608,"value":1487},"離線評估中，DSpark 在 Qwen3 系列模型上相比 Eagle3 的接受 token 長度提升 26.7–30.9%，相比 DFlash 提升 16.3–18.4%。DeepSpec 評估框架覆蓋 GSM8K、MATH500、HumanEval、LiveCodeBench 等九項標準基準，全部開源供社群複現。",{"type":603,"tag":604,"props":1489,"children":1490},{},[1491],{"type":608,"value":1492},"生產環境的數字更為直接：V4 Flash 每用戶生成速度比 MTP-1 基線快 60–85%，Pro 版快 57–78%；依並發程度不同，整體吞吐量提升幅度在 51% 至 400% 之間。這些數字均來自已部署的線上流量，而非實驗室沙盒。",{"type":603,"tag":659,"props":1494,"children":1495},{},[1496],{"type":603,"tag":604,"props":1497,"children":1498},{},[1499,1503,1506],{"type":603,"tag":666,"props":1500,"children":1501},{},[1502],{"type":608,"value":670},{"type":603,"tag":672,"props":1504,"children":1505},{},[],{"type":608,"value":1507},"\nMTP-1(Multi-Token Prediction 1) ：一次前向傳播僅預測 1 個 token 的基礎自回歸解碼策略，是本論文的比較基線。",{"type":603,"tag":647,"props":1509,"children":1511},{"id":1510},"章節四對生產環境-llm-部署的實務影響",[1512],{"type":608,"value":1513},"章節四：對生產環境 LLM 部署的實務影響",{"type":603,"tag":604,"props":1515,"children":1516},{},[1517],{"type":608,"value":1518},"DSpark checkpoints 無需重新訓練基礎模型，可直接插入現有 V4 推理棧，並已在 Gemma 與 Qwen 模型上驗證跨生態系相容性。DeepSpec 以 MIT 授權開源，讓任何團隊都能為自己的模型訓練推測解碼草稿頭。",{"type":603,"tag":604,"props":1520,"children":1521},{},[1522],{"type":608,"value":1523},"對分散式算力網路（如 Akash、io.net）而言，同等硬體可服務的請求數大幅提升，從根本上改變 GPU 租賃的單位經濟學。HN 評論者 lwansbrough 直接點出「這不是貪婪的問題，而是國家安全的問題」——意指中國 AI 實驗室持續的開放發布策略，已成為重塑全球算力競爭格局的政策工具，而非單純的技術慷慨。",{"title":429,"searchDepth":610,"depth":610,"links":1525},[],{"data":1527,"body":1529,"excerpt":-1,"toc":1535},{"title":429,"description":1528},"DSpark 的設計目標是在不動基礎模型的前提下，最大化每次驗證批次的有效 token 接受數。傳統推測解碼的草稿模型為全平行生成，忽略位置間條件依賴；DSpark 以「半自回歸」架構在速度與精度之間取得平衡。",{"type":600,"children":1530},[1531],{"type":603,"tag":604,"props":1532,"children":1533},{},[1534],{"type":608,"value":1528},{"title":429,"searchDepth":610,"depth":610,"links":1536},[],{"data":1538,"body":1540,"excerpt":-1,"toc":1546},{"title":429,"description":1539},"平行草稿主幹同步為所有草稿位置生成基礎 logits，保留高吞吐量優勢。序列注意力頭 (Sequential Head) 以低秩分解 (rank 256) 在採樣前為每個位置疊加前綴條件偏置，使後位置的預測能感知前位置的生成結果，顯著提升草稿序列的語義連貫性。預設採用 Markov 變體（僅依賴前一 token），計算開銷遠低於全序列自回歸草稿。",{"type":600,"children":1541},[1542],{"type":603,"tag":604,"props":1543,"children":1544},{},[1545],{"type":608,"value":1539},{"title":429,"searchDepth":610,"depth":610,"links":1547},[],{"data":1549,"body":1551,"excerpt":-1,"toc":1572},{"title":429,"description":1550},"一個獨立的置信度預測頭以 Sequential Temperature Scaling 校準，估算每個草稿 token 被目標模型接受的概率。校準後預測誤差從 3–8% 壓縮至約 1%，讓排程器能可靠決定哪些序列應延長草稿批次（高置信度）、哪些應提前截止以避免浪費驗證算力（低置信度）。",{"type":600,"children":1552},[1553,1557],{"type":603,"tag":604,"props":1554,"children":1555},{},[1556],{"type":608,"value":1550},{"type":603,"tag":659,"props":1558,"children":1559},{},[1560],{"type":603,"tag":604,"props":1561,"children":1562},{},[1563,1567,1570],{"type":603,"tag":666,"props":1564,"children":1565},{},[1566],{"type":608,"value":670},{"type":603,"tag":672,"props":1568,"children":1569},{},[],{"type":608,"value":1571},"\nSequential Temperature Scaling：一種後處理校準技術，透過學習一個溫度參數調整模型輸出的機率分布，使預測置信度與實際準確率對齊。",{"title":429,"searchDepth":610,"depth":610,"links":1573},[],{"data":1575,"body":1577,"excerpt":-1,"toc":1598},{"title":429,"description":1576},"排程器即時感知 GPU 負載狀態：閒置時延長驗證批次（草稿長度可達 16 token），高負載時縮短批次以降低排隊延遲。實測顯示草稿長度從 4 延伸至 16 token 時每輪延遲僅增加 0.2–1.3%，打破「更長草稿等於更高延遲」的傳統假設。這種動態策略使系統在不同並發等級下都能保持吞吐量最大化。",{"type":600,"children":1578},[1579,1583],{"type":603,"tag":604,"props":1580,"children":1581},{},[1582],{"type":608,"value":1576},{"type":603,"tag":659,"props":1584,"children":1585},{},[1586],{"type":603,"tag":604,"props":1587,"children":1588},{},[1589,1593,1596],{"type":603,"tag":666,"props":1590,"children":1591},{},[1592],{"type":608,"value":1114},{"type":603,"tag":672,"props":1594,"children":1595},{},[],{"type":608,"value":1597},"\n想像一位服務生（草稿模型）一次端上 10 道菜候選，廚師長（目標模型）掃一眼就決定哪道真的上桌。DSpark 的創新是：服務生先和旁邊的同事確認每道菜的搭配是否合理（序列注意力頭），再根據廚師長目前的忙碌程度決定一次端幾道（硬體感知排程），讓廚師長永遠不在等待，也不被淹沒。",{"title":429,"searchDepth":610,"depth":610,"links":1599},[],{"data":1601,"body":1602,"excerpt":-1,"toc":1722},{"title":429,"description":429},{"type":600,"children":1603},[1604,1609,1632,1637,1660,1665,1670,1675,1680,1693,1698,1711,1717],{"type":603,"tag":647,"props":1605,"children":1607},{"id":1606},"競爭版圖",[1608],{"type":608,"value":1606},{"type":603,"tag":1262,"props":1610,"children":1611},{},[1612,1622],{"type":603,"tag":839,"props":1613,"children":1614},{},[1615,1620],{"type":603,"tag":666,"props":1616,"children":1617},{},[1618],{"type":608,"value":1619},"直接競品",{"type":608,"value":1621},"：Eagle3、DFlash（DeepSeek 前代方法）、Medusa（並行草稿頭）、EAGLE（EFT-based 草稿頭）",{"type":603,"tag":839,"props":1623,"children":1624},{},[1625,1630],{"type":603,"tag":666,"props":1626,"children":1627},{},[1628],{"type":608,"value":1629},"間接競品",{"type":608,"value":1631},"：MoE 路由最佳化（降低每次推理激活參數量）、INT4/FP8 量化壓縮提速、模型蒸餾",{"type":603,"tag":647,"props":1633,"children":1635},{"id":1634},"護城河類型",[1636],{"type":608,"value":1634},{"type":603,"tag":1262,"props":1638,"children":1639},{},[1640,1650],{"type":603,"tag":839,"props":1641,"children":1642},{},[1643,1648],{"type":603,"tag":666,"props":1644,"children":1645},{},[1646],{"type":608,"value":1647},"工程護城河",{"type":608,"value":1649},"：置信度排程與硬體感知排程的聯合最佳化難以快速複製；DSpark 在 V4 生產流量上已驗證，具備他人難以短期取得的實戰數據支撐",{"type":603,"tag":839,"props":1651,"children":1652},{},[1653,1658],{"type":603,"tag":666,"props":1654,"children":1655},{},[1656],{"type":608,"value":1657},"生態護城河",{"type":608,"value":1659},"：DeepSpec MIT 授權開源，鼓勵 Gemma、Qwen 社群貢獻草稿頭配置；Hugging Face checkpoints 直接降低採用門檻",{"type":603,"tag":647,"props":1661,"children":1663},{"id":1662},"定價策略",[1664],{"type":608,"value":1662},{"type":603,"tag":604,"props":1666,"children":1667},{},[1668],{"type":608,"value":1669},"DSpark 本身為開源免費 (MIT) ，商業價值體現在兩個層面。其一，DeepSeek API 端點已部署 DSpark，用戶以相同費率獲得 60–85% 速度提升，直接強化 API 性價比競爭力。",{"type":603,"tag":604,"props":1671,"children":1672},{},[1673],{"type":608,"value":1674},"其二，第三方雲端推理供應商（如 Together AI、Replicate）若採用 DeepSpec 自訓草稿頭，可在不升級硬體的前提下大幅提升利潤率。",{"type":603,"tag":647,"props":1676,"children":1678},{"id":1677},"企業導入阻力",[1679],{"type":608,"value":1677},{"type":603,"tag":1262,"props":1681,"children":1682},{},[1683,1688],{"type":603,"tag":839,"props":1684,"children":1685},{},[1686],{"type":608,"value":1687},"大型企業通常採用 vLLM 或 TGI 的穩定版本，升級推理棧有合規與穩定性審查週期",{"type":603,"tag":839,"props":1689,"children":1690},{},[1691],{"type":608,"value":1692},"自訓草稿頭需要與基礎模型規模匹配的算力預算，對中小型部署方不友善",{"type":603,"tag":647,"props":1694,"children":1696},{"id":1695},"第二序影響",[1697],{"type":608,"value":1695},{"type":603,"tag":1262,"props":1699,"children":1700},{},[1701,1706],{"type":603,"tag":839,"props":1702,"children":1703},{},[1704],{"type":608,"value":1705},"GPU 租賃市場單位算力的有效產出提升，可能加速分散式算力網路的商業化進程",{"type":603,"tag":839,"props":1707,"children":1708},{},[1709],{"type":608,"value":1710},"開源推測解碼工具鏈成熟後，「推理速度」作為差異化競爭點的壁壘將下降，推動整體 API 定價下行",{"type":603,"tag":647,"props":1712,"children":1714},{"id":1713},"判決值得關注的基礎設施創新但技術優勢擴散速度快",[1715],{"type":608,"value":1716},"判決：值得關注的基礎設施創新（但技術優勢擴散速度快）",{"type":603,"tag":604,"props":1718,"children":1719},{},[1720],{"type":608,"value":1721},"DSpark 在技術層面是真實的工程突破，生產流量數據可信度高。然而開源策略本身即意味著技術優勢的快速擴散——社群一旦將 DeepSpec 移植到更多模型系列，DeepSeek 的先行優勢將迅速收窄。對雲端推理供應商而言，這是必須跟上的基礎設施升級，而非可忽視的邊際改進。",{"title":429,"searchDepth":610,"depth":610,"links":1723},[],{"data":1725,"body":1726,"excerpt":-1,"toc":1782},{"title":429,"description":429},{"type":600,"children":1727},[1728,1734,1739,1744,1777],{"type":603,"tag":647,"props":1729,"children":1731},{"id":1730},"離線基準比較qwen3-系列",[1732],{"type":608,"value":1733},"離線基準比較（Qwen3 系列）",{"type":603,"tag":604,"props":1735,"children":1736},{},[1737],{"type":608,"value":1738},"DSpark 接受 token 長度相比 Eagle3 提升 26.7–30.9%，相比 DFlash 提升 16.3–18.4%。DeepSpec 評估框架覆蓋九項標準基準（GSM8K、MATH500、HumanEval、LiveCodeBench 等），全部開源供社群複現。",{"type":603,"tag":647,"props":1740,"children":1742},{"id":1741},"生產流量實測",[1743],{"type":608,"value":1741},{"type":603,"tag":1262,"props":1745,"children":1746},{},[1747,1757,1767],{"type":603,"tag":839,"props":1748,"children":1749},{},[1750,1752],{"type":608,"value":1751},"V4 Flash：每用戶生成速度比 MTP-1 快 ",{"type":603,"tag":666,"props":1753,"children":1754},{},[1755],{"type":608,"value":1756},"60–85%",{"type":603,"tag":839,"props":1758,"children":1759},{},[1760,1762],{"type":608,"value":1761},"V4 Pro：每用戶生成速度比 MTP-1 快 ",{"type":603,"tag":666,"props":1763,"children":1764},{},[1765],{"type":608,"value":1766},"57–78%",{"type":603,"tag":839,"props":1768,"children":1769},{},[1770,1772],{"type":608,"value":1771},"整體吞吐量：依並發程度提升 ",{"type":603,"tag":666,"props":1773,"children":1774},{},[1775],{"type":608,"value":1776},"51%–400%",{"type":603,"tag":604,"props":1778,"children":1779},{},[1780],{"type":608,"value":1781},"草稿長度從 4 延伸至 16 token 時，每輪延遲僅增加 0.2–1.3%，驗證硬體感知排程器在高負載下的低開銷特性。",{"title":429,"searchDepth":610,"depth":610,"links":1783},[],{"data":1785,"body":1786,"excerpt":-1,"toc":1807},{"title":429,"description":429},{"type":600,"children":1787},[1788],{"type":603,"tag":1262,"props":1789,"children":1790},{},[1791,1795,1799,1803],{"type":603,"tag":839,"props":1792,"children":1793},{},[1794],{"type":608,"value":256},{"type":603,"tag":839,"props":1796,"children":1797},{},[1798],{"type":608,"value":257},{"type":603,"tag":839,"props":1800,"children":1801},{},[1802],{"type":608,"value":258},{"type":603,"tag":839,"props":1804,"children":1805},{},[1806],{"type":608,"value":259},{"title":429,"searchDepth":610,"depth":610,"links":1808},[],{"data":1810,"body":1811,"excerpt":-1,"toc":1824},{"title":429,"description":429},{"type":600,"children":1812},[1813],{"type":603,"tag":1262,"props":1814,"children":1815},{},[1816,1820],{"type":603,"tag":839,"props":1817,"children":1818},{},[1819],{"type":608,"value":261},{"type":603,"tag":839,"props":1821,"children":1822},{},[1823],{"type":608,"value":262},{"title":429,"searchDepth":610,"depth":610,"links":1825},[],{"data":1827,"body":1828,"excerpt":-1,"toc":1834},{"title":429,"description":266},{"type":600,"children":1829},[1830],{"type":603,"tag":604,"props":1831,"children":1832},{},[1833],{"type":608,"value":266},{"title":429,"searchDepth":610,"depth":610,"links":1835},[],{"data":1837,"body":1838,"excerpt":-1,"toc":1844},{"title":429,"description":267},{"type":600,"children":1839},[1840],{"type":603,"tag":604,"props":1841,"children":1842},{},[1843],{"type":608,"value":267},{"title":429,"searchDepth":610,"depth":610,"links":1845},[],{"data":1847,"body":1848,"excerpt":-1,"toc":1854},{"title":429,"description":322},{"type":600,"children":1849},[1850],{"type":603,"tag":604,"props":1851,"children":1852},{},[1853],{"type":608,"value":322},{"title":429,"searchDepth":610,"depth":610,"links":1855},[],{"data":1857,"body":1858,"excerpt":-1,"toc":1864},{"title":429,"description":325},{"type":600,"children":1859},[1860],{"type":603,"tag":604,"props":1861,"children":1862},{},[1863],{"type":608,"value":325},{"title":429,"searchDepth":610,"depth":610,"links":1865},[],{"data":1867,"body":1868,"excerpt":-1,"toc":1874},{"title":429,"description":327},{"type":600,"children":1869},[1870],{"type":603,"tag":604,"props":1871,"children":1872},{},[1873],{"type":608,"value":327},{"title":429,"searchDepth":610,"depth":610,"links":1875},[],{"data":1877,"body":1878,"excerpt":-1,"toc":1884},{"title":429,"description":330},{"type":600,"children":1879},[1880],{"type":603,"tag":604,"props":1881,"children":1882},{},[1883],{"type":608,"value":330},{"title":429,"searchDepth":610,"depth":610,"links":1885},[],{"data":1887,"body":1888,"excerpt":-1,"toc":2035},{"title":429,"description":429},{"type":600,"children":1889},[1890,1896,1901,1906,1911,1917,1922,1942,1947,1952,1958,1963,1968,1973,1978,2001,2007,2012,2017,2022],{"type":603,"tag":647,"props":1891,"children":1893},{"id":1892},"章節一改裝者自述如何將消費級-gpu-偽裝成高記憶體版本",[1894],{"type":608,"value":1895},"章節一：改裝者自述——如何將消費級 GPU 偽裝成高記憶體版本",{"type":603,"tag":604,"props":1897,"children":1898},{},[1899],{"type":608,"value":1900},"2026 年 6 月，一位自述親手改裝過 GPU 的 r/LocalLLaMA 用戶公開聲稱：市面上所有宣傳的 96GB+ RTX 4090 和 RTX 5090，本質上都是詐騙——因為他本人就做這種改裝。",{"type":603,"tag":604,"props":1902,"children":1903},{},[1904],{"type":608,"value":1905},"48GB 版本的 4090 改裝流程：取得翻新的 GPU 核心，搭配客製雙面 PCB（類似伺服器 GPU 的「clamshell」設計），前後各焊接 12 顆 GDDR6X 記憶體晶片共 24 顆，再刷入從 NVIDIA 內部外洩的 BIOS 工具，強制驅動程式識別新的記憶體配置。整個流程需要工業等級焊接設備與液冷系統，成品噪音約 65 分貝，屬工廠噪音等級。",{"type":603,"tag":604,"props":1907,"children":1908},{},[1909],{"type":608,"value":1910},"至於 96GB 版本，改裝者本人直接承認是「道聽塗說」。物理現實是：RTX 4090 的 384 位元記憶體匯流排共 12 個通道，要達到 96GB 每通道需要 4GB 的 GDDR6X 模組，但此規格市場根本不存在，現有上限僅為 2GB。深圳廠商聲稱持有「特殊料件」，但迄今無任何公開驗證，所有標榜 96GB 的改裝 4090 在技術層面即為不可能存在之物。",{"type":603,"tag":647,"props":1912,"children":1914},{"id":1913},"章節二為何改裝卡無法真正提升-ai-工作負載效能",[1915],{"type":608,"value":1916},"章節二：為何改裝卡無法真正提升 AI 工作負載效能",{"type":603,"tag":604,"props":1918,"children":1919},{},[1920],{"type":608,"value":1921},"即使改裝卡的 VRAM 擴充「成功」，對本地 LLM 推論的效能提升幾乎為零。推論效能的瓶頸從來都不是 VRAM 容量，而是記憶體頻寬。",{"type":603,"tag":659,"props":1923,"children":1924},{},[1925],{"type":603,"tag":604,"props":1926,"children":1927},{},[1928,1932,1935,1940],{"type":603,"tag":666,"props":1929,"children":1930},{},[1931],{"type":608,"value":670},{"type":603,"tag":672,"props":1933,"children":1934},{},[],{"type":603,"tag":666,"props":1936,"children":1937},{},[1938],{"type":608,"value":1939},"decode phase（解碼階段）",{"type":608,"value":1941},"：LLM 逐字產生 token 的過程。每產生一個 token，GPU 需完整讀取一遍模型權重，速度完全受限於記憶體頻寬 (GB/s) ，而非算力 (TFLOPS) 。",{"type":603,"tag":604,"props":1943,"children":1944},{},[1945],{"type":608,"value":1946},"Token 生成速度由頻寬決定：頻寬提升 78%，生成速度就能提升接近 78%；TFLOPS 只影響初始提示詞的處理速度 (prefill) ，對 token 生成影響極小。RTX 4090 的頻寬約 1,008 GB/s，這個數字不會因 VRAM 從 24GB 擴充到 48GB 甚至 96GB 而改變——384 位元匯流排寬度固定，頻寬就固定。",{"type":603,"tag":604,"props":1948,"children":1949},{},[1950],{"type":608,"value":1951},"RTX 5090 採用 GDDR7，頻寬達 1,792 GB/s，比 4090 提升約 77%，這才是真正影響推論速度的升級。然而 5090 僅有 32GB VRAM，連載入完整的 70B Q4 模型（約需 40GB）都不夠，市場街頭價更已達 3,695–4,800 美元，遠超官方建議售價 1,999 美元。改裝卡能讓你載入更大的模型，但每秒 token 數與原廠 4090 分毫不差。",{"type":603,"tag":647,"props":1953,"children":1955},{"id":1954},"章節三如何辨識與避免購入改裝詐騙卡",[1956],{"type":608,"value":1957},"章節三：如何辨識與避免購入改裝詐騙卡",{"type":603,"tag":604,"props":1959,"children":1960},{},[1961],{"type":608,"value":1962},"這個市場存在四個層次的詐騙，複雜程度遠超一般消費者預期。",{"type":603,"tag":604,"props":1964,"children":1965},{},[1966],{"type":608,"value":1967},"第一層「完全假冒」：GPU 核心與 VRAM 均為假品，原廠標記物理磨除後以雷射重蝕，外觀幾近完美。Tom's Hardware 報導的維修技師拆解後稱：「這是我見過最強的詐騙。」第二層「空殼詐騙」：外殼使用正品（如 Asus TUF RTX 4090），但核心與記憶體已被摘除，常見於 eBay「Amazon 棧板貨」話術。",{"type":603,"tag":604,"props":1969,"children":1970},{},[1971],{"type":608,"value":1972},"第三層「世代偽裝」：30 系列晶片改裝後偽裝成 40 系列出售。Tom's Hardware 記錄到一名技師收到的 4 張 RTX 4090 中有 3 張採用此手法。第四層「虛假規格改裝」：宣稱 96GB 但實際容量未達標或穩定性極差，反而是四層中最少見的一種。",{"type":603,"tag":604,"props":1974,"children":1975},{},[1976],{"type":608,"value":1977},"識別方式：",{"type":603,"tag":1262,"props":1979,"children":1980},{},[1981,1986,1991,1996],{"type":603,"tag":839,"props":1982,"children":1983},{},[1984],{"type":608,"value":1985},"使用 GPU-Z 確認實際 VRAM 大小與 BIOS 版本（外洩 BIOS 通常含異常字串）",{"type":603,"tag":839,"props":1987,"children":1988},{},[1989],{"type":608,"value":1990},"透過 HWiNFO 檢查記憶體頻率與通道數是否符合原廠規格",{"type":603,"tag":839,"props":1992,"children":1993},{},[1994],{"type":608,"value":1995},"觀察散熱器是否異常巨大或採用非原廠設計",{"type":603,"tag":839,"props":1997,"children":1998},{},[1999],{"type":608,"value":2000},"避免透過 eBay、AliExpress 購買宣稱「工廠尾貨」「棧板拆件」的高價改裝卡",{"type":603,"tag":647,"props":2002,"children":2004},{"id":2003},"章節四gpu-記憶體需求暴增下的灰色市場生態",[2005],{"type":608,"value":2006},"章節四：GPU 記憶體需求暴增下的灰色市場生態",{"type":603,"tag":604,"props":2008,"children":2009},{},[2010],{"type":608,"value":2011},"這條灰色供應鏈的根源，部分來自美國對中國的 GPU 出口管制。高端 NVIDIA GPU 無法合規進入中國，卻催生了一條複雜的替代路徑：深圳部分工廠以合規方式進口已拆除核心與 VRAM 的顯卡外殼，再於國內自行安裝升級版記憶體，拆除的原廠零件則流入二手市場，有時偽裝成完整顯卡出售。",{"type":603,"tag":604,"props":2013,"children":2014},{},[2015],{"type":608,"value":2016},"隨著本地 LLM 社群對 VRAM 需求快速攀升（70B 模型需 48GB、120B+ 需 96GB），灰色供應鏈規模持續擴張，詐騙行為也更難追蹤。改裝卡故障率比原廠高出 15–20%，企業級 GPU 在相同情境下僅約 5–8%，在無保固的灰色市場中故障即等於全損。",{"type":603,"tag":604,"props":2018,"children":2019},{},[2020],{"type":608,"value":2021},"目前真正具備高 CP 值的合規替代方案：",{"type":603,"tag":1262,"props":2023,"children":2024},{},[2025,2030],{"type":603,"tag":839,"props":2026,"children":2027},{},[2028],{"type":608,"value":2029},"雙 RTX 3090 + NVLink 橋接（48GB 合計容量，約 1,600–1,800 美元，有原廠保固）",{"type":603,"tag":839,"props":2031,"children":2032},{},[2033],{"type":608,"value":2034},"等待 RTX Pro 6000 Blackwell（96GB GDDR7，預估 8,500–10,000 美元）",{"title":429,"searchDepth":610,"depth":610,"links":2036},[],{"data":2038,"body":2040,"excerpt":-1,"toc":2046},{"title":429,"description":2039},"96GB 改裝 4090 的騙局在技術層面站不住腳，關鍵在於一個不可繞過的物理限制：現有 GDDR6X 記憶體模組的規格上限。",{"type":600,"children":2041},[2042],{"type":603,"tag":604,"props":2043,"children":2044},{},[2045],{"type":608,"value":2039},{"title":429,"searchDepth":610,"depth":610,"links":2047},[],{"data":2049,"body":2051,"excerpt":-1,"toc":2077},{"title":429,"description":2050},"RTX 4090 採用 384 位元記憶體匯流排，共 12 個通道。要達到 48GB，每通道需要 2GB 的 GDDR6X 模組——這已是目前市場上限。要達到 96GB，每通道需要 4GB 模組，此規格至今從未商業量產，深圳廠商聲稱的「特殊料件」也無公開驗證紀錄。",{"type":600,"children":2052},[2053,2057],{"type":603,"tag":604,"props":2054,"children":2055},{},[2056],{"type":608,"value":2050},{"type":603,"tag":659,"props":2058,"children":2059},{},[2060],{"type":603,"tag":604,"props":2061,"children":2062},{},[2063,2067,2070,2075],{"type":603,"tag":666,"props":2064,"children":2065},{},[2066],{"type":608,"value":670},{"type":603,"tag":672,"props":2068,"children":2069},{},[],{"type":603,"tag":666,"props":2071,"children":2072},{},[2073],{"type":608,"value":2074},"GDDR6X",{"type":608,"value":2076},"：高端消費級 GPU 常用的視訊記憶體規格，由美光 (Micron) 生產。現有晶粒設計每顆容量最大為 2GB，要達到 4GB／顆需要全新晶粒設計，目前尚未量產。",{"title":429,"searchDepth":610,"depth":610,"links":2078},[],{"data":2080,"body":2082,"excerpt":-1,"toc":2103},{"title":429,"description":2081},"48GB 改裝版需採用特製「雙面 PCB（clamshell 設計）」，前後各焊接 12 顆 GDDR6X 晶片共 24 顆，再刷入從 NVIDIA 內部外洩的 BIOS 工具，強制驅動程式識別新配置。整個過程需要工業等級焊接設備，且外洩 BIOS 來源違規，存在法律與安全風險，成品噪音約 65 分貝（工廠等級）。",{"type":600,"children":2083},[2084,2088],{"type":603,"tag":604,"props":2085,"children":2086},{},[2087],{"type":608,"value":2081},{"type":603,"tag":659,"props":2089,"children":2090},{},[2091],{"type":603,"tag":604,"props":2092,"children":2093},{},[2094,2098,2101],{"type":603,"tag":666,"props":2095,"children":2096},{},[2097],{"type":608,"value":1114},{"type":603,"tag":672,"props":2099,"children":2100},{},[],{"type":608,"value":2102},"\n就像把 12 格飲料托盤換成雙面 24 格托盤——只要結構撐得住，確實能多裝；但若宣稱同一個托盤能放 48 格，那是謊言，因為根本沒有那種尺寸的杯子。",{"title":429,"searchDepth":610,"depth":610,"links":2104},[],{"data":2106,"body":2108,"excerpt":-1,"toc":2114},{"title":429,"description":2107},"不論 VRAM 從 24GB 擴充到 48GB 或 96GB，RTX 4090 的 384 位元匯流排與約 1,008 GB/s 頻寬完全不變。在 LLM decode 階段，每產生一個 token 就需要完整讀取模型權重，速度受限於頻寬。改裝卡能讓你載入更大的模型，但每秒 token 數與原廠 4090 分毫不差——真正帶來速度提升的是更高頻寬，而非更大容量。",{"type":600,"children":2109},[2110],{"type":603,"tag":604,"props":2111,"children":2112},{},[2113],{"type":608,"value":2107},{"title":429,"searchDepth":610,"depth":610,"links":2115},[],{"data":2117,"body":2118,"excerpt":-1,"toc":2230},{"title":429,"description":429},{"type":600,"children":2119},[2120,2124,2145,2149,2171,2175,2180,2184,2202,2206,2219,2225],{"type":603,"tag":647,"props":2121,"children":2122},{"id":1606},[2123],{"type":608,"value":1606},{"type":603,"tag":1262,"props":2125,"children":2126},{},[2127,2136],{"type":603,"tag":839,"props":2128,"children":2129},{},[2130,2134],{"type":603,"tag":666,"props":2131,"children":2132},{},[2133],{"type":608,"value":1619},{"type":608,"value":2135},"：原廠 RTX 4090（24GB，二手約 1,600 美元）、RTX 5090（32GB，街頭價 3,695–4,800 美元）、雙 RTX 3090 NVLink（48GB，1,600–1,800 美元）",{"type":603,"tag":839,"props":2137,"children":2138},{},[2139,2143],{"type":603,"tag":666,"props":2140,"children":2141},{},[2142],{"type":608,"value":1629},{"type":608,"value":2144},"：NVIDIA A100/H100 企業卡（80GB HBM2e，以雲端租用為主）、Apple Silicon（統一記憶體最高 192GB，但 CUDA 生態不相容）",{"type":603,"tag":647,"props":2146,"children":2147},{"id":1634},[2148],{"type":608,"value":1634},{"type":603,"tag":1262,"props":2150,"children":2151},{},[2152,2161],{"type":603,"tag":839,"props":2153,"children":2154},{},[2155,2159],{"type":603,"tag":666,"props":2156,"children":2157},{},[2158],{"type":608,"value":1647},{"type":608,"value":2160},"：NVIDIA CUDA 生態系不可繞過——PyTorch、TensorRT 均以 CUDA 為第一公民，改裝卡即使技術上可用，也必須依賴 NVIDIA 驅動程式",{"type":603,"tag":839,"props":2162,"children":2163},{},[2164,2169],{"type":603,"tag":666,"props":2165,"children":2166},{},[2167],{"type":608,"value":2168},"供應鏈護城河",{"type":608,"value":2170},"：GDDR6X 模組由美光獨家供應，更高容量模組的量產完全取決於 NVIDIA 與美光的商業決策，灰色市場無法自行生產",{"type":603,"tag":647,"props":2172,"children":2173},{"id":1662},[2174],{"type":608,"value":1662},{"type":603,"tag":604,"props":2176,"children":2177},{},[2178],{"type":608,"value":2179},"NVIDIA 在消費卡（RTX 5090 MSRP 1,999 美元，32GB）與專業卡（RTX Pro 6000 Blackwell 約 8,500–10,000 美元，96GB）之間刻意留下定價斷層。這個斷層正是改裝市場存在的根本原因——有 48–96GB VRAM 需求的用戶，在原廠產品線幾乎找不到中間選項。",{"type":603,"tag":647,"props":2181,"children":2182},{"id":1677},[2183],{"type":608,"value":1677},{"type":603,"tag":1262,"props":2185,"children":2186},{},[2187,2192,2197],{"type":603,"tag":839,"props":2188,"children":2189},{},[2190],{"type":608,"value":2191},"改裝卡無法進入合規採購流程（缺乏原廠保固與技術支援文件）",{"type":603,"tag":839,"props":2193,"children":2194},{},[2195],{"type":608,"value":2196},"外洩 BIOS 的法律風險使企業 IT 部門難以背書",{"type":603,"tag":839,"props":2198,"children":2199},{},[2200],{"type":608,"value":2201},"15–20% 的故障率遠超企業 SLA 容忍上限（一般要求 \u003C1%）",{"type":603,"tag":647,"props":2203,"children":2204},{"id":1695},[2205],{"type":608,"value":1695},{"type":603,"tag":1262,"props":2207,"children":2208},{},[2209,2214],{"type":603,"tag":839,"props":2210,"children":2211},{},[2212],{"type":608,"value":2213},"灰色市場盛行反而替 NVIDIA 驗證了「48–96GB VRAM 消費市場需求真實存在」，可能加速 RTX Pro 6000 Blackwell 的量產節奏",{"type":603,"tag":839,"props":2215,"children":2216},{},[2217],{"type":608,"value":2218},"出口管制繞道效應：管制愈嚴，深圳「合規拆件再改裝」的灰色產業愈旺",{"type":603,"tag":647,"props":2220,"children":2222},{"id":2221},"判決護城河穩固但定價斷層是-nvidia-自己種下的因灰色市場短期只會擴張",[2223],{"type":608,"value":2224},"判決：護城河穩固，但定價斷層是 NVIDIA 自己種下的因（灰色市場短期只會擴張）",{"type":603,"tag":604,"props":2226,"children":2227},{},[2228],{"type":608,"value":2229},"技術護城河與供應鏈控制讓 NVIDIA 無可撼動，但消費卡與專業卡之間的 6–8 倍定價差，為詐騙者提供了充足的生存空間。在 RTX Pro 6000 Blackwell 普及前，灰色市場與相關詐騙案例只會增加，不會減少。",{"title":429,"searchDepth":610,"depth":610,"links":2231},[],{"data":2233,"body":2234,"excerpt":-1,"toc":2406},{"title":429,"description":429},{"type":600,"children":2235},[2236,2242,2348,2353,2401],{"type":603,"tag":647,"props":2237,"children":2239},{"id":2238},"頻寬對比影響-llm-decode-速度",[2240],{"type":608,"value":2241},"頻寬對比（影響 LLM decode 速度）",{"type":603,"tag":2243,"props":2244,"children":2245},"table",{},[2246,2275],{"type":603,"tag":2247,"props":2248,"children":2249},"thead",{},[2250],{"type":603,"tag":2251,"props":2252,"children":2253},"tr",{},[2254,2260,2265,2270],{"type":603,"tag":2255,"props":2256,"children":2257},"th",{},[2258],{"type":608,"value":2259},"GPU",{"type":603,"tag":2255,"props":2261,"children":2262},{},[2263],{"type":608,"value":2264},"記憶體頻寬",{"type":603,"tag":2255,"props":2266,"children":2267},{},[2268],{"type":608,"value":2269},"VRAM 容量",{"type":603,"tag":2255,"props":2271,"children":2272},{},[2273],{"type":608,"value":2274},"備註",{"type":603,"tag":2276,"props":2277,"children":2278},"tbody",{},[2279,2303,2325],{"type":603,"tag":2251,"props":2280,"children":2281},{},[2282,2288,2293,2298],{"type":603,"tag":2283,"props":2284,"children":2285},"td",{},[2286],{"type":608,"value":2287},"RTX 4090 原廠",{"type":603,"tag":2283,"props":2289,"children":2290},{},[2291],{"type":608,"value":2292},"~1,008 GB/s",{"type":603,"tag":2283,"props":2294,"children":2295},{},[2296],{"type":608,"value":2297},"24 GB GDDR6X",{"type":603,"tag":2283,"props":2299,"children":2300},{},[2301],{"type":608,"value":2302},"消費級頂規基準線",{"type":603,"tag":2251,"props":2304,"children":2305},{},[2306,2311,2315,2320],{"type":603,"tag":2283,"props":2307,"children":2308},{},[2309],{"type":608,"value":2310},"48GB 改裝 4090",{"type":603,"tag":2283,"props":2312,"children":2313},{},[2314],{"type":608,"value":2292},{"type":603,"tag":2283,"props":2316,"children":2317},{},[2318],{"type":608,"value":2319},"48 GB GDDR6X",{"type":603,"tag":2283,"props":2321,"children":2322},{},[2323],{"type":608,"value":2324},"頻寬不變，token 速度與原廠相同",{"type":603,"tag":2251,"props":2326,"children":2327},{},[2328,2333,2338,2343],{"type":603,"tag":2283,"props":2329,"children":2330},{},[2331],{"type":608,"value":2332},"RTX 5090",{"type":603,"tag":2283,"props":2334,"children":2335},{},[2336],{"type":608,"value":2337},"1,792 GB/s",{"type":603,"tag":2283,"props":2339,"children":2340},{},[2341],{"type":608,"value":2342},"32 GB GDDR7",{"type":603,"tag":2283,"props":2344,"children":2345},{},[2346],{"type":608,"value":2347},"頻寬提升 77%，VRAM 仍不足 70B Q4",{"type":603,"tag":647,"props":2349,"children":2351},{"id":2350},"故障率對比",[2352],{"type":608,"value":2350},{"type":603,"tag":2243,"props":2354,"children":2355},{},[2356,2372],{"type":603,"tag":2247,"props":2357,"children":2358},{},[2359],{"type":603,"tag":2251,"props":2360,"children":2361},{},[2362,2367],{"type":603,"tag":2255,"props":2363,"children":2364},{},[2365],{"type":608,"value":2366},"GPU 類型",{"type":603,"tag":2255,"props":2368,"children":2369},{},[2370],{"type":608,"value":2371},"故障率",{"type":603,"tag":2276,"props":2373,"children":2374},{},[2375,2388],{"type":603,"tag":2251,"props":2376,"children":2377},{},[2378,2383],{"type":603,"tag":2283,"props":2379,"children":2380},{},[2381],{"type":608,"value":2382},"改裝 GPU（灰色市場）",{"type":603,"tag":2283,"props":2384,"children":2385},{},[2386],{"type":608,"value":2387},"15–20%",{"type":603,"tag":2251,"props":2389,"children":2390},{},[2391,2396],{"type":603,"tag":2283,"props":2392,"children":2393},{},[2394],{"type":608,"value":2395},"企業級 GPU（原廠）",{"type":603,"tag":2283,"props":2397,"children":2398},{},[2399],{"type":608,"value":2400},"5–8%",{"type":603,"tag":604,"props":2402,"children":2403},{},[2404],{"type":608,"value":2405},"改裝卡故障率是企業級 GPU 的 2–4 倍，且在無保固的灰色市場中故障即等同全損。",{"title":429,"searchDepth":610,"depth":610,"links":2407},[],{"data":2409,"body":2410,"excerpt":-1,"toc":2427},{"title":429,"description":429},{"type":600,"children":2411},[2412],{"type":603,"tag":1262,"props":2413,"children":2414},{},[2415,2419,2423],{"type":603,"tag":839,"props":2416,"children":2417},{},[2418],{"type":608,"value":336},{"type":603,"tag":839,"props":2420,"children":2421},{},[2422],{"type":608,"value":337},{"type":603,"tag":839,"props":2424,"children":2425},{},[2426],{"type":608,"value":338},{"title":429,"searchDepth":610,"depth":610,"links":2428},[],{"data":2430,"body":2431,"excerpt":-1,"toc":2448},{"title":429,"description":429},{"type":600,"children":2432},[2433],{"type":603,"tag":1262,"props":2434,"children":2435},{},[2436,2440,2444],{"type":603,"tag":839,"props":2437,"children":2438},{},[2439],{"type":608,"value":340},{"type":603,"tag":839,"props":2441,"children":2442},{},[2443],{"type":608,"value":341},{"type":603,"tag":839,"props":2445,"children":2446},{},[2447],{"type":608,"value":342},{"title":429,"searchDepth":610,"depth":610,"links":2449},[],{"data":2451,"body":2452,"excerpt":-1,"toc":2458},{"title":429,"description":346},{"type":600,"children":2453},[2454],{"type":603,"tag":604,"props":2455,"children":2456},{},[2457],{"type":608,"value":346},{"title":429,"searchDepth":610,"depth":610,"links":2459},[],{"data":2461,"body":2462,"excerpt":-1,"toc":2468},{"title":429,"description":347},{"type":600,"children":2463},[2464],{"type":603,"tag":604,"props":2465,"children":2466},{},[2467],{"type":608,"value":347},{"title":429,"searchDepth":610,"depth":610,"links":2469},[],{"data":2471,"body":2472,"excerpt":-1,"toc":2516},{"title":429,"description":429},{"type":600,"children":2473},[2474,2480,2485,2491,2496,2511],{"type":603,"tag":647,"props":2475,"children":2477},{"id":2476},"intel-股價復甦背後的-ai-轉型",[2478],{"type":608,"value":2479},"Intel 股價復甦背後的 AI 轉型",{"type":603,"tag":604,"props":2481,"children":2482},{},[2483],{"type":608,"value":2484},"2026 年 4 月 24 日 Intel 股價單日暴漲 24%，創 1987 年以來最大單日漲幅，年度累計漲幅逾 250%。Q1 財報連續第六季超預期，AI 相關營收佔比從不足 25% 躍升至約 60%，資料中心業務年增 22%。Intel Xeon 6 搭配 Nvidia GPU 已成超大型雲端業者的標準機架配置，Apple 合作在美製造晶片的消息則再度引發新一波飆升。",{"type":603,"tag":647,"props":2486,"children":2488},{"id":2487},"gaudi-3-的性價比邏輯與社群爭議",[2489],{"type":608,"value":2490},"Gaudi 3 的性價比邏輯與社群爭議",{"type":603,"tag":604,"props":2492,"children":2493},{},[2494],{"type":608,"value":2495},"Gaudi 3 搭載 128 GB HBM2e，在 Llama 2 70B 推論宣稱比 H100 多 20% 吞吐量，硬體售價僅約一半。然而對陣 H200 時吞吐量縮至 80–110%，MoE 大模型推論差距更明顯。",{"type":603,"tag":659,"props":2497,"children":2498},{},[2499],{"type":603,"tag":604,"props":2500,"children":2501},{},[2502,2506,2509],{"type":603,"tag":666,"props":2503,"children":2504},{},[2505],{"type":608,"value":670},{"type":603,"tag":672,"props":2507,"children":2508},{},[],{"type":608,"value":2510},"\nMoE(Mixture of Experts) ：大模型架構的一種，每次推論只啟動部分「專家」子網路，在維持效能的同時降低計算成本，DeepSeek V4 即採此設計。",{"type":603,"tag":604,"props":2512,"children":2513},{},[2514],{"type":608,"value":2515},"社群分歧明顯：懷疑派認為軟體生態尚不成熟，支持派則指出 Xeon CPU 推論是不依賴 CUDA 的務實替代方案。",{"title":429,"searchDepth":610,"depth":610,"links":2517},[],{"data":2519,"body":2521,"excerpt":-1,"toc":2532},{"title":429,"description":2520},"Intel A770 用戶早已親歷非 Nvidia 平台的軟體生態困境——跑 LLM 幾乎需要完全複製開發者的環境，包含特定版本 Python 與所有函式庫。",{"type":600,"children":2522},[2523,2527],{"type":603,"tag":604,"props":2524,"children":2525},{},[2526],{"type":608,"value":2520},{"type":603,"tag":604,"props":2528,"children":2529},{},[2530],{"type":608,"value":2531},"Gaudi 3 在 cost-sensitive 部署場景的性價比數字確實誘人，但 CUDA 生態的護城河不只是硬體算力，而是多年積累的工具鏈。若工作負載是標準 Llama 推論且預算受限，值得 PoC；若需要最前沿 MoE 模型，建議等軟體支援更成熟再行動。",{"title":429,"searchDepth":610,"depth":610,"links":2533},[],{"data":2535,"body":2537,"excerpt":-1,"toc":2548},{"title":429,"description":2536},"Intel 的復甦有結構性支撐：AI 相關營收佔比突破 60%、美國政府持有近 10% 股份提供政策背書、CEO Lip-Bu Tan 積極推進晶圓代工轉型。",{"type":600,"children":2538},[2539,2543],{"type":603,"tag":604,"props":2540,"children":2541},{},[2542],{"type":608,"value":2536},{"type":603,"tag":604,"props":2544,"children":2545},{},[2546],{"type":608,"value":2547},"對企業採購決策者而言，Intel Xeon 推論路線提供了一條不依賴 Nvidia 生態的退路。在地緣政治風險與 GPU 供貨壓力下，這張牌的戰略價值遠超過純技術性能的比較。",{"title":429,"searchDepth":610,"depth":610,"links":2549},[],{"data":2551,"body":2552,"excerpt":-1,"toc":2588},{"title":429,"description":429},{"type":600,"children":2553},[2554,2560],{"type":603,"tag":647,"props":2555,"children":2557},{"id":2556},"效能基準gaudi-3-對比",[2558],{"type":608,"value":2559},"效能基準（Gaudi 3 對比）",{"type":603,"tag":1262,"props":2561,"children":2562},{},[2563,2568,2573,2578,2583],{"type":603,"tag":839,"props":2564,"children":2565},{},[2566],{"type":608,"value":2567},"LLaMA 2 70B 推論：比 H100 多 20% 吞吐量（Gaudi 3 宣稱）",{"type":603,"tag":839,"props":2569,"children":2570},{},[2571],{"type":608,"value":2572},"Llama 3 80B（Dell 平台）：性價比優於 H100 達 70%",{"type":603,"tag":839,"props":2574,"children":2575},{},[2576],{"type":608,"value":2577},"對陣 H200：吞吐量約 80–110%",{"type":603,"tag":839,"props":2579,"children":2580},{},[2581],{"type":608,"value":2582},"硬體定價：8 張 Gaudi 3 系統 $157,613 vs 8 張 H100 $300,107（差距約 1.9x）",{"type":603,"tag":839,"props":2584,"children":2585},{},[2586],{"type":608,"value":2587},"弱點：batch size > 32 的 MoE 大模型推論明顯落後 H200/B200",{"title":429,"searchDepth":610,"depth":610,"links":2589},[],{"data":2591,"body":2592,"excerpt":-1,"toc":2641},{"title":429,"description":429},{"type":600,"children":2593},[2594,2600,2605,2620,2625,2631,2636],{"type":603,"tag":647,"props":2595,"children":2597},{"id":2596},"兩種-ai-模式工具還是主人",[2598],{"type":608,"value":2599},"兩種 AI 模式：工具還是主人？",{"type":603,"tag":604,"props":2601,"children":2602},{},[2603],{"type":608,"value":2604},"Cory Doctorow 新書《The Reverse Centaur's Guide to Life After AI》提出核心框架：「Centaur（人輔機器）」由人類主導工具；「Reverse Centaur（機器指揮人）」讓演算法指揮工人——如 Amazon 倉庫，工傷率高達同業 3 倍。",{"type":603,"tag":659,"props":2606,"children":2607},{},[2608],{"type":603,"tag":604,"props":2609,"children":2610},{},[2611,2615,2618],{"type":603,"tag":666,"props":2612,"children":2613},{},[2614],{"type":608,"value":670},{"type":603,"tag":672,"props":2616,"children":2617},{},[],{"type":608,"value":2619},"\nReverse Centaur：演算法像主人一樣指揮人類行動，而非人類使用 AI 工具；工人淪為系統的手腳而非駕駛者。",{"type":603,"tag":604,"props":2621,"children":2622},{},[2623],{"type":608,"value":2624},"放射科 AI 是最具警示的案例：公司計畫裁撤 90% 醫師，讓留下的一人只需點擊 OK 確認自動報告，成為問責吸收器——負法律責任，卻無實質決策權。",{"type":603,"tag":647,"props":2626,"children":2628},{"id":2627},"ai-泡沫與集體行動",[2629],{"type":608,"value":2630},"AI 泡沫與集體行動",{"type":603,"tag":604,"props":2632,"children":2633},{},[2634],{"type":608,"value":2635},"AI 已投入約 1.4 兆美元，年營收僅 500 億美元，且規模越大越虧。Doctorow 認為這是大型科技公司面臨市場飽和後製造的成長敘事泡沫。",{"type":603,"tag":604,"props":2637,"children":2638},{},[2639],{"type":608,"value":2640},"好萊塢編劇罷工 (WGA) 透過行業集體談判成功守住邊界；加州 Monterey Park 公投永久禁止新建資料中心——皆為可複製的草根行動模型。",{"title":429,"searchDepth":610,"depth":610,"links":2642},[],{"data":2644,"body":2646,"excerpt":-1,"toc":2657},{"title":429,"description":2645},"當公司要求「導入 AI 工具」時，Doctorow 的框架提供清醒判斷基準：若 AI 減少重複勞動、提升產品品質，是 Centaur 模式；若目的是裁減高薪職位、讓演算法取代專業判斷，就是 Reverse Centaur。",{"type":600,"children":2647},[2648,2652],{"type":603,"tag":604,"props":2649,"children":2650},{},[2651],{"type":608,"value":2645},{"type":603,"tag":604,"props":2653,"children":2654},{},[2655],{"type":608,"value":2656},"後泡沫期的預測同樣值得注意：資料中心與 GPU 將大量流入市場，開源模型將快速最佳化——對工程師而言，這可能是技術機會的開始，而非終點。",{"title":429,"searchDepth":610,"depth":610,"links":2658},[],{"data":2660,"body":2662,"excerpt":-1,"toc":2673},{"title":429,"description":2661},"1.4 兆美元投入、500 億美元產出——AI 泡沫的財務邏輯根本不成立。對企業決策者而言，在泡沫破裂前跟風投入 AI 基礎建設，可能面臨重大沈沒成本。",{"type":600,"children":2663},[2664,2668],{"type":603,"tag":604,"props":2665,"children":2666},{},[2667],{"type":608,"value":2661},{"type":603,"tag":604,"props":2669,"children":2670},{},[2671],{"type":608,"value":2672},"更深遠的品牌風險在於：若 AI 實際用於裁撤高薪工人、輸出劣質服務，消費者信任損失難以量化。好萊塢集體談判模式，可能預告其他行業工會的下一波 AI 條款要求。",{"title":429,"searchDepth":610,"depth":610,"links":2674},[],{"data":2676,"body":2677,"excerpt":-1,"toc":2735},{"title":429,"description":429},{"type":600,"children":2678},[2679,2685,2690,2705,2720,2725,2730],{"type":603,"tag":647,"props":2680,"children":2682},{"id":2681},"什麼是遮罩擴散語言模型",[2683],{"type":608,"value":2684},"什麼是遮罩擴散語言模型？",{"type":603,"tag":604,"props":2686,"children":2687},{},[2688],{"type":608,"value":2689},"iLLaDA(Improved LLaDA) 由中國人民大學與 ByteDance 聯合開發，是一個 80 億參數的遮罩擴散語言模型，採用完整雙向注意力架構，生成時從遮罩佔位符出發，經多次平行迭代精煉，而非逐字依序輸出。",{"type":603,"tag":659,"props":2691,"children":2692},{},[2693],{"type":603,"tag":604,"props":2694,"children":2695},{},[2696,2700,2703],{"type":603,"tag":666,"props":2697,"children":2698},{},[2699],{"type":608,"value":670},{"type":603,"tag":672,"props":2701,"children":2702},{},[],{"type":608,"value":2704},"\n遮罩擴散語言模型 (Masked Diffusion LM) ：生成時先把全句設為空白遮罩，再逐輪預測並還原各位置的字，類似圖像擴散模型的去噪過程，但應用於文字。",{"type":603,"tag":659,"props":2706,"children":2707},{},[2708],{"type":603,"tag":604,"props":2709,"children":2710},{},[2711,2715,2718],{"type":603,"tag":666,"props":2712,"children":2713},{},[2714],{"type":608,"value":1114},{"type":603,"tag":672,"props":2716,"children":2717},{},[],{"type":608,"value":2719},"\n傳統 LLM 像從左到右逐字填空；iLLaDA 則像先把整段文字打滿馬賽克，再一輪一輪擦掉最有把握的部分，直到全部還原。",{"type":603,"tag":647,"props":2721,"children":2723},{"id":2722},"訓練規模與基準成績",[2724],{"type":608,"value":2722},{"type":603,"tag":604,"props":2726,"children":2727},{},[2728],{"type":608,"value":2729},"預訓練語料達 12 兆 token（前代 LLaDA 僅 2.3 兆），Base 版本平均分 63.9，微幅超越 Qwen2.5 7B(63.3) 。",{"type":603,"tag":604,"props":2731,"children":2732},{},[2733],{"type":608,"value":2734},"Instruct 版本得分 67.1，落後 Qwen2.5 7B Instruct(77.1) 約 10 分，主因是缺乏強化學習對齊訓練。模型已於 GitHub(ML-GSAI/LLaDA) 完整開源。",{"title":429,"searchDepth":610,"depth":610,"links":2736},[],{"data":2738,"body":2740,"excerpt":-1,"toc":2751},{"title":429,"description":2739},"iLLaDA 的雙向注意力讓模型在生成時能看到所有位置的上下文，理論上對結構化輸出和全域一致性有優勢。",{"type":600,"children":2741},[2742,2746],{"type":603,"tag":604,"props":2743,"children":2744},{},[2745],{"type":608,"value":2739},{"type":603,"tag":604,"props":2747,"children":2748},{},[2749],{"type":608,"value":2750},"但目前 HumanEval 僅 50.0，Instruct 版本明顯落後，主因是尚未引入 RLHF 或 RLVR 對齊訓練。若有興趣評估此架構，可直接從 GitHub(ML-GSAI/LLaDA) 拉取權重進行本地實驗。",{"title":429,"searchDepth":610,"depth":610,"links":2752},[],{"data":2754,"body":2756,"excerpt":-1,"toc":2767},{"title":429,"description":2755},"iLLaDA 目前是研究里程碑，而非可部署的生產模型。Base 版本在學術基準上與 Qwen2.5 7B 持平，但 Instruct 版本差距明顯，短期內難以取代現有自回歸模型。",{"type":600,"children":2757},[2758,2762],{"type":603,"tag":604,"props":2759,"children":2760},{},[2761],{"type":608,"value":2755},{"type":603,"tag":604,"props":2763,"children":2764},{},[2765],{"type":608,"value":2766},"長期意義在於：若擴散語言模型能補足對齊訓練的缺口，平行生成架構有望在延遲敏感場景（如長文本生成）提供差異化優勢。",{"title":429,"searchDepth":610,"depth":610,"links":2768},[],{"data":2770,"body":2771,"excerpt":-1,"toc":2811},{"title":429,"description":429},{"type":600,"children":2772},[2773,2778],{"type":603,"tag":647,"props":2774,"children":2776},{"id":2775},"效能基準",[2777],{"type":608,"value":2775},{"type":603,"tag":1262,"props":2779,"children":2780},{},[2781,2786,2791,2796,2801,2806],{"type":603,"tag":839,"props":2782,"children":2783},{},[2784],{"type":608,"value":2785},"MMLU：74.8",{"type":603,"tag":839,"props":2787,"children":2788},{},[2789],{"type":608,"value":2790},"BBH：71.3",{"type":603,"tag":839,"props":2792,"children":2793},{},[2794],{"type":608,"value":2795},"GSM8K：81.9",{"type":603,"tag":839,"props":2797,"children":2798},{},[2799],{"type":608,"value":2800},"HumanEval：50.0",{"type":603,"tag":839,"props":2802,"children":2803},{},[2804],{"type":608,"value":2805},"iLLaDA-Base 平均：63.9（Qwen2.5 7B：63.3）",{"type":603,"tag":839,"props":2807,"children":2808},{},[2809],{"type":608,"value":2810},"iLLaDA-Instruct 平均：67.1（Qwen2.5 7B Instruct：77.1）",{"title":429,"searchDepth":610,"depth":610,"links":2812},[],{"data":2814,"body":2815,"excerpt":-1,"toc":2893},{"title":429,"description":429},{"type":600,"children":2816},[2817,2822,2827,2832,2837,2842,2860,2865,2888],{"type":603,"tag":647,"props":2818,"children":2820},{"id":2819},"關鍵調查數據",[2821],{"type":608,"value":2819},{"type":603,"tag":604,"props":2823,"children":2824},{},[2825],{"type":608,"value":2826},"Anthropic 於 2026 年 6 月 27 日發布針對約 9,700 名 Claude 用戶的調查報告，橫跨 Chat、Cowork、Code 三個使用模式。約 50% 受訪者認為 AI 已能處理自身 50% 或以上的工作任務，其中 33% 估計涵蓋 30–60%、14% 達到 60–90%，4% 更認為 Claude 幾乎能完成整份工作。",{"type":603,"tag":604,"props":2828,"children":2829},{},[2830],{"type":608,"value":2831},"展望未來 12 個月，26–35% 的受訪者預期 AI 將接管大部分工作，近 60% 預期覆蓋率將比現在更高。",{"type":603,"tag":647,"props":2833,"children":2835},{"id":2834},"生產力正向回報",[2836],{"type":608,"value":2834},{"type":603,"tag":604,"props":2838,"children":2839},{},[2840],{"type":608,"value":2841},"使用率最高的三大工作類型：",{"type":603,"tag":835,"props":2843,"children":2844},{},[2845,2850,2855],{"type":603,"tag":839,"props":2846,"children":2847},{},[2848],{"type":608,"value":2849},"資料庫查詢 (82%)",{"type":603,"tag":839,"props":2851,"children":2852},{},[2853],{"type":608,"value":2854},"部落格／文章寫作 (81%)",{"type":603,"tag":839,"props":2856,"children":2857},{},[2858],{"type":608,"value":2859},"行銷內容 (80%)",{"type":603,"tag":604,"props":2861,"children":2862},{},[2863],{"type":608,"value":2864},"整體生產力回報：",{"type":603,"tag":1262,"props":2866,"children":2867},{},[2868,2873,2878,2883],{"type":603,"tag":839,"props":2869,"children":2870},{},[2871],{"type":608,"value":2872},"86% 感受到速度提升",{"type":603,"tag":839,"props":2874,"children":2875},{},[2876],{"type":608,"value":2877},"82% 感受到工作範疇擴大",{"type":603,"tag":839,"props":2879,"children":2880},{},[2881],{"type":608,"value":2882},"69% 認為品質改善",{"type":603,"tag":839,"props":2884,"children":2885},{},[2886],{"type":608,"value":2887},"57% 認為自身技能更有價值",{"type":603,"tag":604,"props":2889,"children":2890},{},[2891],{"type":608,"value":2892},"一個反直覺發現：將更多任務委託給 Claude 的用戶，對未來薪資與技能價值反而更樂觀——與外界對 AI 取代就業的普遍擔憂相悖。但仍有 10% 受訪者認為自己在 12 個月內「可能或非常可能」失業，三分之一擔憂初階同事的工作保障。",{"title":429,"searchDepth":610,"depth":610,"links":2894},[],{"data":2896,"body":2897,"excerpt":-1,"toc":2903},{"title":429,"description":472},{"type":600,"children":2898},[2899],{"type":603,"tag":604,"props":2900,"children":2901},{},[2902],{"type":608,"value":472},{"title":429,"searchDepth":610,"depth":610,"links":2904},[],{"data":2906,"body":2907,"excerpt":-1,"toc":2913},{"title":429,"description":473},{"type":600,"children":2908},[2909],{"type":603,"tag":604,"props":2910,"children":2911},{},[2912],{"type":608,"value":473},{"title":429,"searchDepth":610,"depth":610,"links":2914},[],{"data":2916,"body":2917,"excerpt":-1,"toc":2973},{"title":429,"description":429},{"type":600,"children":2918},[2919,2925,2930,2935,2940,2945,2968],{"type":603,"tag":647,"props":2920,"children":2922},{"id":2921},"反諷的-10-億美元",[2923],{"type":608,"value":2924},"反諷的 10 億美元",{"type":603,"tag":604,"props":2926,"children":2927},{},[2928],{"type":608,"value":2929},"2026 年 6 月 27 日，前美國商務部長 Gina Raimondo 與前印第安納州長 Eric Holcomb 聯合創立非黨派非營利組織「Raise Us」，目標募集 10 億美元（已到位 5 億）用於 AI 時代勞動力再培訓。",{"type":603,"tag":604,"props":2931,"children":2932},{},[2933],{"type":608,"value":2934},"贊助企業橫跨 AI 開發商與傳統產業：Amazon、Anthropic、Microsoft、OpenAI Foundation、AMD、IBM、General Motors、Mastercard 等 18 家以上，美國銀行 (Bank of America) 為主要贊助商，資助先進製造業學徒計畫。",{"type":603,"tag":647,"props":2936,"children":2938},{"id":2937},"四大核心計畫",[2939],{"type":608,"value":2937},{"type":603,"tag":604,"props":2941,"children":2942},{},[2943],{"type":608,"value":2944},"計畫分四軌推進：",{"type":603,"tag":835,"props":2946,"children":2947},{},[2948,2953,2958,2963],{"type":603,"tag":839,"props":2949,"children":2950},{},[2951],{"type":608,"value":2952},"州級夥伴關係（阿肯色、康乃狄克、馬里蘭、猶他四州試點，跨兩黨執政）",{"type":603,"tag":839,"props":2954,"children":2955},{},[2956],{"type":608,"value":2957},"雇主聯盟（開發再培訓與留才試點）",{"type":603,"tag":839,"props":2959,"children":2960},{},[2961],{"type":608,"value":2962},"教育訓練（擴展 AI 驅動的非傳統大學替代方案）",{"type":603,"tag":839,"props":2964,"children":2965},{},[2966],{"type":608,"value":2967},"政策實驗室（開發新政策方向，由非企業資金支應）",{"type":603,"tag":604,"props":2969,"children":2970},{},[2971],{"type":608,"value":2972},"這是 AI 頂尖開發商首次聯合為勞動力轉型投入如此規模的資金。",{"title":429,"searchDepth":610,"depth":610,"links":2974},[],{"data":2976,"body":2978,"excerpt":-1,"toc":3004},{"title":429,"description":2977},"從數據看，現實不太樂觀。美國主要聯邦再培訓計畫 (WIOA) 顯示，45% 的參與者回流至原本產業，27% 留在同一職種，成功轉型比例低於 15%。",{"type":600,"children":2979},[2980,2984,2999],{"type":603,"tag":604,"props":2981,"children":2982},{},[2983],{"type":608,"value":2977},{"type":603,"tag":659,"props":2985,"children":2986},{},[2987],{"type":603,"tag":604,"props":2988,"children":2989},{},[2990,2994,2997],{"type":603,"tag":666,"props":2991,"children":2992},{},[2993],{"type":608,"value":670},{"type":603,"tag":672,"props":2995,"children":2996},{},[],{"type":608,"value":2998},"\nWIOA(Workforce Innovation and Opportunity Act) ：美國聯邦勞動力培訓主要法案，補助州政府提供職業訓練與就業媒合服務。",{"type":603,"tag":604,"props":3000,"children":3001},{},[3002],{"type":608,"value":3003},"Raise Us 的關鍵在於「雇主聯盟」能否提供真實職缺，而非只是結業證書。若有機會參與試點，評估重點應放在計畫是否直接對接用人單位。",{"title":429,"searchDepth":610,"depth":610,"links":3005},[],{"data":3007,"body":3009,"excerpt":-1,"toc":3020},{"title":429,"description":3008},"這是 AI 開發商首次集體承認就業衝擊責任，具有雙重戰略意義：一是轉移社會責任壓力，二是確保自動化技術的政治可行性。",{"type":600,"children":3010},[3011,3015],{"type":603,"tag":604,"props":3012,"children":3013},{},[3014],{"type":608,"value":3008},{"type":603,"tag":604,"props":3016,"children":3017},{},[3018],{"type":608,"value":3019},"若計畫成效良好，AI 公司將獲得更強的正當性繼續推進自動化；若效果有限，「我們有出資培訓」的說法反而可能加速監管反彈。這是一場攸關 AI 產業社會合法性的長期賭注。",{"title":429,"searchDepth":610,"depth":610,"links":3021},[],{"data":3023,"body":3024,"excerpt":-1,"toc":3103},{"title":429,"description":429},{"type":600,"children":3025},[3026,3032,3053,3058,3073,3079,3091],{"type":603,"tag":647,"props":3027,"children":3029},{"id":3028},"真正可編輯的-pptx不是截圖",[3030],{"type":608,"value":3031},"真正可編輯的 PPTX，不是截圖",{"type":603,"tag":604,"props":3033,"children":3034},{},[3035,3037,3042,3044,3051],{"type":608,"value":3036},"ppt-master 由財務專業人士 Hugo He 開發，MIT 授權開源，截至 2026 年 6 月已累積 ",{"type":603,"tag":666,"props":3038,"children":3039},{},[3040],{"type":608,"value":3041},"33,100 顆 GitHub Stars",{"type":608,"value":3043},"。它能從 PDF、DOCX、圖片、URL 等任意來源，透過 AI 生成真正可在 PowerPoint 中點選編輯的 ",{"type":603,"tag":3045,"props":3046,"children":3048},"code",{"className":3047},[],[3049],{"type":608,"value":3050},".pptx",{"type":608,"value":3052}," 檔案。",{"type":603,"tag":604,"props":3054,"children":3055},{},[3056],{"type":608,"value":3057},"與多數「截圖式」AI 簡報工具最關鍵的差異在於：ppt-master 輸出的是 OOXML 原生 DrawingML 物件——每個形狀、文字框、圖表都能直接修改，而非鎖死的圖片層。",{"type":603,"tag":659,"props":3059,"children":3060},{},[3061],{"type":603,"tag":604,"props":3062,"children":3063},{},[3064,3068,3071],{"type":603,"tag":666,"props":3065,"children":3066},{},[3067],{"type":608,"value":670},{"type":603,"tag":672,"props":3069,"children":3070},{},[],{"type":608,"value":3072},"\nDrawingML 是 Office Open XML(OOXML) 規範中定義圖形的標準，PowerPoint 的所有形狀與圖表皆以此為基礎，輸出 DrawingML 等於輸出「原生可編輯的 PowerPoint 元素」。",{"type":603,"tag":647,"props":3074,"children":3076},{"id":3075},"功能演進動畫語音旁白模板繼承",[3077],{"type":608,"value":3078},"功能演進：動畫、語音旁白、模板繼承",{"type":603,"tag":604,"props":3080,"children":3081},{},[3082,3084,3089],{"type":608,"value":3083},"v2.5.0 起支援每元素進場動畫與頁面轉場效果，演講者備忘錄可輸出為語音旁白並封裝進 ",{"type":603,"tag":3045,"props":3085,"children":3087},{"className":3086},[],[3088],{"type":608,"value":3050},{"type":608,"value":3090},"，原生在 PowerPoint 播放。",{"type":603,"tag":604,"props":3092,"children":3093},{},[3094,3096,3101],{"type":608,"value":3095},"使用者可提供現有 ",{"type":603,"tag":3045,"props":3097,"children":3099},{"className":3098},[],[3100],{"type":608,"value":3050},{"type":608,"value":3102}," 作為模板，工具會自動萃取主題色彩、字型與母版結構，套用至新生成內容，無需重新設計。",{"title":429,"searchDepth":610,"depth":610,"links":3104},[],{"data":3106,"body":3108,"excerpt":-1,"toc":3119},{"title":429,"description":3107},"工具以 Python 為核心，採 SVG → DrawingML 轉換管線，可作為「skill」在 Claude Code、Cursor、VS Code + Copilot 等 AI IDE 中以對話介面驅動。",{"type":600,"children":3109},[3110,3114],{"type":603,"tag":604,"props":3111,"children":3112},{},[3113],{"type":608,"value":3107},{"type":603,"tag":604,"props":3115,"children":3116},{},[3117],{"type":608,"value":3118},"模型無關，支援 GPT、Gemini 等主流 LLM，但作者明確建議搭配大上下文 Claude Opus 以獲最佳輸出品質。目前文件側重 IDE skill 整合，若需嵌入 CI/CD 或 REST API，須自行包裝 Python 呼叫層。",{"title":429,"searchDepth":610,"depth":610,"links":3120},[],{"data":3122,"body":3124,"excerpt":-1,"toc":3135},{"title":429,"description":3123},"MIT 授權讓企業可自由部署於內部工作流，無授權費用疑慮。33,100 Stars 的快速成長代表社群正在形成，周邊整合方案有望湧現。",{"type":600,"children":3125},[3126,3130],{"type":603,"tag":604,"props":3127,"children":3128},{},[3129],{"type":608,"value":3123},{"type":603,"tag":604,"props":3131,"children":3132},{},[3133],{"type":608,"value":3134},"對商用 AI 簡報 SaaS（如 Gamma、Beautiful.ai）形成生態壓力——開源工具已支援動畫、語音旁白與模板繼承，付費方案需重新思考差異化定位。中小企業採用開源路線可顯著降低簡報製作成本。",{"title":429,"searchDepth":610,"depth":610,"links":3136},[],{"data":3138,"body":3139,"excerpt":-1,"toc":3203},{"title":429,"description":429},{"type":600,"children":3140},[3141,3147,3152,3167,3172,3177,3183,3188],{"type":603,"tag":647,"props":3142,"children":3144},{"id":3143},"一個-c-runtime整合-14-種音訊模型",[3145],{"type":608,"value":3146},"一個 C++ Runtime，整合 14 種音訊模型",{"type":603,"tag":604,"props":3148,"children":3149},{},[3150],{"type":608,"value":3151},"audio.cpp 是基於 ggml 框架打造的純 C++ 音訊推論引擎，不需要任何 Python 依賴。",{"type":603,"tag":659,"props":3153,"children":3154},{},[3155],{"type":603,"tag":604,"props":3156,"children":3157},{},[3158,3162,3165],{"type":603,"tag":666,"props":3159,"children":3160},{},[3161],{"type":608,"value":1114},{"type":603,"tag":672,"props":3163,"children":3164},{},[],{"type":608,"value":3166},"\n就像 llama.cpp 把 LLM 從 Python 解放出來，audio.cpp 對音訊模型做了同樣的事。",{"type":603,"tag":604,"props":3168,"children":3169},{},[3170],{"type":608,"value":3171},"目前涵蓋 14 個模型，包括 Qwen3-TTS（10 語言）、PocketTTS（100M 參數）、Chatterbox（18 語言）、OmniVoice（646+ 語言），以及 Silero VAD、Sortformer 說話者分離等。",{"type":603,"tag":604,"props":3173,"children":3174},{},[3175],{"type":608,"value":3176},"底層支援 CPU、CUDA、Vulkan、Metal 四種後端，並提供 REST API 伺服器供服務整合。",{"type":603,"tag":647,"props":3178,"children":3180},{"id":3179},"效能有多快",[3181],{"type":608,"value":3182},"效能有多快？",{"type":603,"tag":604,"props":3184,"children":3185},{},[3186],{"type":608,"value":3187},"CUDA 環境下，TTS 速度比 Python 快 1.83x—5.03x。長文本實時率 (RTF) 更亮眼：PocketTTS 達 48x 實時速度，Kokoro TTS 達 51x。",{"type":603,"tag":659,"props":3189,"children":3190},{},[3191],{"type":603,"tag":604,"props":3192,"children":3193},{},[3194,3198,3201],{"type":603,"tag":666,"props":3195,"children":3196},{},[3197],{"type":608,"value":670},{"type":603,"tag":672,"props":3199,"children":3200},{},[],{"type":608,"value":3202},"\nRTF(Real-Time Factor) ：值越低代表推論越快，RTF = 0.032 代表生成 1 秒音訊只需 32 毫秒。",{"title":429,"searchDepth":610,"depth":610,"links":3204},[],{"data":3206,"body":3208,"excerpt":-1,"toc":3219},{"title":429,"description":3207},"audio.cpp 提供 C API，可直接以 FFI 從 Go、Rust、Node.js 呼叫，無需啟動 Python 子程序。REST API 伺服器支援 JSON workflow 定義，遷移現有 TTS/ASR pipeline 的整合成本低。",{"type":600,"children":3209},[3210,3214],{"type":603,"tag":604,"props":3211,"children":3212},{},[3213],{"type":608,"value":3207},{"type":603,"tag":604,"props":3215,"children":3216},{},[3217],{"type":608,"value":3218},"主要注意事項：Q8_0 量化在部分模型路徑可能出現異常，建議先以預設精度驗證功能。專案仍在快速迭代（首發 12 個模型，現已 14 個），生產部署前應鎖定特定 commit 版本。",{"title":429,"searchDepth":610,"depth":610,"links":3220},[],{"data":3222,"body":3224,"excerpt":-1,"toc":3235},{"title":429,"description":3223},"音訊 AI 功能（TTS、語音辨識）長期依賴雲端 API，帶來延遲與成本壓力。audio.cpp 提供可本地部署的替代路徑，在消費級 GPU 上即可達實時以上速度。",{"type":600,"children":3225},[3226,3230],{"type":603,"tag":604,"props":3227,"children":3228},{},[3229],{"type":608,"value":3223},{"type":603,"tag":604,"props":3231,"children":3232},{},[3233],{"type":608,"value":3234},"5x 加速比意味著相同硬體可服務更多並發請求，或直接縮減 GPU 租用成本。OmniVoice 的 646+ 語言支援，對需多語種覆蓋的全球化產品具有直接商業價值。",{"title":429,"searchDepth":610,"depth":610,"links":3236},[],{"data":3238,"body":3239,"excerpt":-1,"toc":3296},{"title":429,"description":429},{"type":600,"children":3240},[3241,3245,3250,3268,3273],{"type":603,"tag":647,"props":3242,"children":3243},{"id":2775},[3244],{"type":608,"value":2775},{"type":603,"tag":604,"props":3246,"children":3247},{},[3248],{"type":608,"value":3249},"CUDA 環境下 TTS 速度比 Python 參考實作：",{"type":603,"tag":1262,"props":3251,"children":3252},{},[3253,3258,3263],{"type":603,"tag":839,"props":3254,"children":3255},{},[3256],{"type":608,"value":3257},"VeVo2：5.03x",{"type":603,"tag":839,"props":3259,"children":3260},{},[3261],{"type":608,"value":3262},"PocketTTS：3.68x",{"type":603,"tag":839,"props":3264,"children":3265},{},[3266],{"type":608,"value":3267},"Qwen3-TTS：1.83x",{"type":603,"tag":604,"props":3269,"children":3270},{},[3271],{"type":608,"value":3272},"RTF（實時率）：",{"type":603,"tag":1262,"props":3274,"children":3275},{},[3276,3281,3286,3291],{"type":603,"tag":839,"props":3277,"children":3278},{},[3279],{"type":608,"value":3280},"PocketTTS 短文本：0.032（31x 實時速度）",{"type":603,"tag":839,"props":3282,"children":3283},{},[3284],{"type":608,"value":3285},"PocketTTS 長文本：48.40x 實時速度",{"type":603,"tag":839,"props":3287,"children":3288},{},[3289],{"type":608,"value":3290},"Kokoro TTS 長文本：51.60x 實時速度",{"type":603,"tag":839,"props":3292,"children":3293},{},[3294],{"type":608,"value":3295},"Q8_0 量化：降低 VRAM 約 25%，速度提升 3.6—3.8%",{"title":429,"searchDepth":610,"depth":610,"links":3297},[],{"data":3299,"body":3300,"excerpt":-1,"toc":3376},{"title":429,"description":429},{"type":600,"children":3301},[3302,3307,3328,3361,3366,3371],{"type":603,"tag":647,"props":3303,"children":3305},{"id":3304},"漏洞批量公開的新模式",[3306],{"type":608,"value":3304},{"type":603,"tag":604,"props":3308,"children":3309},{},[3310,3312,3318,3320,3326],{"type":608,"value":3311},"匿名 GitHub 帳號 ",{"type":603,"tag":3045,"props":3313,"children":3315},{"className":3314},[],[3316],{"type":608,"value":3317},"bikini",{"type":608,"value":3319}," 於 2026 年 6 月底發布 ",{"type":603,"tag":3045,"props":3321,"children":3323},{"className":3322},[],[3324],{"type":608,"value":3325},"exploitarium",{"type":608,"value":3327}," 資料庫，收錄大量未回報零日漏洞的 PoC，並公開邀請他人取走 CVE 署名，理由是「引人入門最有效率的方式」。資安機構 Femtosec 確認三個漏洞屬真實有效：",{"type":603,"tag":1262,"props":3329,"children":3330},{},[3331,3341,3351],{"type":603,"tag":839,"props":3332,"children":3333},{},[3334,3339],{"type":603,"tag":666,"props":3335,"children":3336},{},[3337],{"type":608,"value":3338},"CVE-2026-55200",{"type":608,"value":3340},"：libssh2 heap overflow(CVSS 9.2) ，pre-authentication 即可觸發遠端程式碼執行",{"type":603,"tag":839,"props":3342,"children":3343},{},[3344,3349],{"type":603,"tag":666,"props":3345,"children":3346},{},[3347],{"type":608,"value":3348},"CVE-2026-20896",{"type":608,"value":3350},"：Gitea 認證繞過 (CVSS 9.8)",{"type":603,"tag":839,"props":3352,"children":3353},{},[3354,3359],{"type":603,"tag":666,"props":3355,"children":3356},{},[3357],{"type":608,"value":3358},"CVE-2025-62408",{"type":608,"value":3360},"：c-ares DoS",{"type":603,"tag":647,"props":3362,"children":3364},{"id":3363},"零日公開的升溫趨勢",[3365],{"type":608,"value":3363},{"type":603,"tag":604,"props":3367,"children":3368},{},[3369],{"type":608,"value":3370},"此事件並非孤例。2026 年 4 月，研究員「Chaotic Eclipse」公開 BlueHammer(CVE-2026-33825) ，利用五個合法 Windows 功能鏈實現本地提權 (LPE) 至 SYSTEM；BlueHammer 等三個 CVE 均已在野積極遭利用。",{"type":603,"tag":604,"props":3372,"children":3373},{},[3374],{"type":608,"value":3375},"微軟已公開批評此類做法並移除相關研究員的 GitHub 帳號，業界責任揭露規範的邊界爭議持續升溫。",{"title":429,"searchDepth":610,"depth":610,"links":3377},[],{"data":3379,"body":3381,"excerpt":-1,"toc":3392},{"title":429,"description":3380},"nmap parser 漏洞引發最多討論——若成立，任何執行 nmap 掃描的主機均可觸發 reverse shell，評論者稱「這是情報機構夢寐以求的漏洞類型」。",{"type":600,"children":3382},[3383,3387],{"type":603,"tag":604,"props":3384,"children":3385},{},[3386],{"type":608,"value":3380},{"type":603,"tag":604,"props":3388,"children":3389},{},[3390],{"type":608,"value":3391},"實務建議：立即確認 libssh2 與 Gitea 版本並套用修補；CVSS 9+ 漏洞應視為緊急變更，不要等待常規補丁週期。部分條目疑為 LLM 輔助挖掘未經篩選，品質不一，不可全盤信任清單內容。",{"title":429,"searchDepth":610,"depth":610,"links":3393},[],{"data":3395,"body":3397,"excerpt":-1,"toc":3408},{"title":429,"description":3396},"微軟移除研究員帳號的舉動引發社群反彈，但也凸顯困境：公開揭露縮短了企業的應對窗口，讓攻擊者與防禦者同時取得 exploit。",{"type":600,"children":3398},[3399,3403],{"type":603,"tag":604,"props":3400,"children":3401},{},[3402],{"type":608,"value":3396},{"type":603,"tag":604,"props":3404,"children":3405},{},[3406],{"type":608,"value":3407},"若此趨勢持續，企業將面臨更密集的緊急修補週期，SOC 資源壓力升高。若匿名行為者無法被業界規範約束，平台政策乃至立法介入的呼聲將進一步強化。",{"title":429,"searchDepth":610,"depth":610,"links":3409},[],{"data":3411,"body":3412,"excerpt":-1,"toc":3442},{"title":429,"description":429},{"type":600,"children":3413},[3414,3419],{"type":603,"tag":647,"props":3415,"children":3417},{"id":3416},"漏洞嚴重性評分",[3418],{"type":608,"value":3416},{"type":603,"tag":1262,"props":3420,"children":3421},{},[3422,3427,3432,3437],{"type":603,"tag":839,"props":3423,"children":3424},{},[3425],{"type":608,"value":3426},"CVE-2026-55200(libssh2 heap overflow) ：CVSS 9.2",{"type":603,"tag":839,"props":3428,"children":3429},{},[3430],{"type":608,"value":3431},"CVE-2026-20896（Gitea 認證繞過）：CVSS 9.8",{"type":603,"tag":839,"props":3433,"children":3434},{},[3435],{"type":608,"value":3436},"CVE-2025-62408(c-ares DoS) ：CVSS 未公告",{"type":603,"tag":839,"props":3438,"children":3439},{},[3440],{"type":608,"value":3441},"BlueHammer CVE-2026-33825(Windows LPE) ：已在野積極利用",{"title":429,"searchDepth":610,"depth":610,"links":3443},[],{"data":3445,"body":3446,"excerpt":-1,"toc":3523},{"title":429,"description":429},{"type":600,"children":3447},[3448,3453,3458,3463,3468,3473,3478,3483,3488,3493,3498,3503,3508,3513,3518],{"type":603,"tag":647,"props":3449,"children":3451},{"id":3450},"社群熱議排行",[3452],{"type":608,"value":3450},{"type":603,"tag":604,"props":3454,"children":3455},{},[3456],{"type":608,"value":3457},"今日前三熱議：Anthropic Mythos 遭美國政府管控（HN/X 多串討論）、後訓練革命讓小型模型逼近商用水準（Reddit r/LocalLLaMA 高互動）、DeepSeek DSpark 推測解碼開源（HN + Bluesky 廣傳）。",{"type":603,"tag":604,"props":3459,"children":3460},{},[3461],{"type":608,"value":3462},"另兩大熱議：96GB 改裝 GPU 詐騙手法曝光（HN 強烈反應）、半數 Claude 用戶將過半工作交給 AI（HN/Bluesky 反應兩極）。HN 對 Mythos 管控傾向政治解讀：lwansbrough 直言「這不是貪婪，而是國家安全問題。」",{"type":603,"tag":647,"props":3464,"children":3466},{"id":3465},"技術爭議與分歧",[3467],{"type":608,"value":3465},{"type":603,"tag":604,"props":3469,"children":3470},{},[3471],{"type":608,"value":3472},"VRAM 市場是今日最大社群分歧。jmyeet(HN) 痛批：「5090 售價 3,000–4,000 美元只有 32GB，RTX 6000 Pro 有 96GB 卻要 11,000 美元。」",{"type":603,"tag":604,"props":3474,"children":3475},{},[3476],{"type":608,"value":3477},"microgpt(HN) 以諷刺回應：「中國：看看我們逆向工程出來的 GPU，要不要用 NVIDIA 一半的價格買一張 RTX 5090？」",{"type":603,"tag":604,"props":3479,"children":3480},{},[3481],{"type":608,"value":3482},"另一戰線在 AI 投資回報上。slimdude.ca（Bluesky，42 讚）引用 Doctorow：「AI 每年只賺了 5 千萬美元，但每年卻投入數十億美元——請保持懷疑。」",{"type":603,"tag":647,"props":3484,"children":3486},{"id":3485},"實戰經驗",[3487],{"type":608,"value":3485},{"type":603,"tag":604,"props":3489,"children":3490},{},[3491],{"type":608,"value":3492},"u/entsnack(Reddit r/LocalLLaMA) 親身揭露：「Cursor 的模型確實是後訓練版的 Kimi K2。一個後訓練的小型本地 LLM，可以媲美沒有後訓練的大型商業模型。」",{"type":603,"tag":604,"props":3494,"children":3495},{},[3496],{"type":608,"value":3497},"HN 用戶 anon373839 補充數字：「GLM-5.2 完整 RL 訓練——讓它在 agentic 任務可靠的部分——只花了兩天。後訓練比預訓練便宜且快速得多。」",{"type":603,"tag":604,"props":3499,"children":3500},{},[3501],{"type":608,"value":3502},"dlcarrier(HN) 踩坑警告：Intel A770 跑 Stable Diffusion 沒問題，但 LLM 卡關，「AI 這塊技術債比一般軟體工程還嚴重——你幾乎得完全複製開發者當時的環境。」",{"type":603,"tag":647,"props":3504,"children":3506},{"id":3505},"未解問題與社群預期",[3507],{"type":608,"value":3505},{"type":603,"tag":604,"props":3509,"children":3510},{},[3511],{"type":608,"value":3512},"@theobearman(X) 指出，Mythos 附錄 A 核准名單目前無任何外國機構，包括 UKAISI 在內。歐洲能否透過外交取得豁免，社群尚無答案。",{"type":603,"tag":604,"props":3514,"children":3515},{},[3516],{"type":608,"value":3517},"jmyeet(HN) 預測 5090 要到 2028–2029 年才換代，48–64GB 中間選項短期不會出現——VRAM 飢渴是 NVIDIA 刻意為之的市場策略，而非技術限制。",{"type":603,"tag":604,"props":3519,"children":3520},{},[3521],{"type":608,"value":3522},"grayhatter(HN) 就零日事件警告：「沙盒的首要目的是保護你免受你所信任的應用程式中的零日漏洞攻擊。」匿名批量公開漏洞的責任邊界，仍是社群待解的懸案。",{"title":429,"searchDepth":610,"depth":610,"links":3524},[],{"data":3526,"body":3528,"excerpt":-1,"toc":3539},{"title":429,"description":3527},"今日 AI 圖景呈現弔詭的雙軌現象：頂端存取愈來愈管制（Mythos 只給「受信任」組織），底層能力卻愈來愈民主化（後訓練讓小型模型逼近商用大模型，DSpark 讓開源推論成本再降）。",{"type":600,"children":3529},[3530,3534],{"type":603,"tag":604,"props":3531,"children":3532},{},[3533],{"type":608,"value":3527},{"type":603,"tag":604,"props":3535,"children":3536},{},[3537],{"type":608,"value":3538},"當半數用戶已將過半工作量交給 AI，下一個真正的問題不是「AI 能不能做到」，而是「誰決定你能不能用這個 AI」。",{"title":429,"searchDepth":610,"depth":610,"links":3540},[],{"data":3542,"body":3543,"excerpt":-1,"toc":3729},{"title":429,"description":429},{"type":600,"children":3544},[3545,3550,3555,3561,3667,3672,3677,3682,3700,3705,3723],{"type":603,"tag":647,"props":3546,"children":3548},{"id":3547},"環境需求",[3549],{"type":608,"value":3547},{"type":603,"tag":604,"props":3551,"children":3552},{},[3553],{"type":608,"value":3554},"DSpark checkpoints 已上傳至 Hugging Face（DeepSeek-V4-Pro-DSpark 與 DeepSeek-V4-Flash-DSpark），以標準 transformers 或 vLLM 載入即可。DeepSpec 訓練代碼庫以 MIT 授權開源，支援 Python 3.10+ 環境，依賴 PyTorch 2.x，推薦搭配 vLLM 或 SGLang 作為推理後端。",{"type":603,"tag":647,"props":3556,"children":3558},{"id":3557},"最小-poc",[3559],{"type":608,"value":3560},"最小 PoC",{"type":603,"tag":3562,"props":3563,"children":3567},"pre",{"className":3564,"code":3565,"language":3566,"meta":429,"style":429},"language-bash shiki shiki-themes vitesse-dark","pip install vllm\npython -m vllm.entrypoints.openai.api_server \\\n  --model deepseek-ai/DeepSeek-V4-Flash-DSpark \\\n  --speculative-model deepseek-ai/DeepSeek-V4-Flash-DSpark-Draft \\\n  --num-speculative-tokens 8\n","bash",[3568],{"type":603,"tag":3045,"props":3569,"children":3570},{"__ignoreMap":429},[3571,3594,3618,3636,3653],{"type":603,"tag":3572,"props":3573,"children":3576},"span",{"class":3574,"line":3575},"line",1,[3577,3583,3589],{"type":603,"tag":3572,"props":3578,"children":3580},{"style":3579},"--shiki-default:#80A665",[3581],{"type":608,"value":3582},"pip",{"type":603,"tag":3572,"props":3584,"children":3586},{"style":3585},"--shiki-default:#C98A7D",[3587],{"type":608,"value":3588}," install",{"type":603,"tag":3572,"props":3590,"children":3591},{"style":3585},[3592],{"type":608,"value":3593}," vllm\n",{"type":603,"tag":3572,"props":3595,"children":3596},{"class":3574,"line":610},[3597,3602,3608,3613],{"type":603,"tag":3572,"props":3598,"children":3599},{"style":3579},[3600],{"type":608,"value":3601},"python",{"type":603,"tag":3572,"props":3603,"children":3605},{"style":3604},"--shiki-default:#C99076",[3606],{"type":608,"value":3607}," -m",{"type":603,"tag":3572,"props":3609,"children":3610},{"style":3585},[3611],{"type":608,"value":3612}," vllm.entrypoints.openai.api_server",{"type":603,"tag":3572,"props":3614,"children":3615},{"style":3604},[3616],{"type":608,"value":3617}," \\\n",{"type":603,"tag":3572,"props":3619,"children":3621},{"class":3574,"line":3620},3,[3622,3627,3632],{"type":603,"tag":3572,"props":3623,"children":3624},{"style":3604},[3625],{"type":608,"value":3626},"  --model",{"type":603,"tag":3572,"props":3628,"children":3629},{"style":3585},[3630],{"type":608,"value":3631}," deepseek-ai/DeepSeek-V4-Flash-DSpark",{"type":603,"tag":3572,"props":3633,"children":3634},{"style":3604},[3635],{"type":608,"value":3617},{"type":603,"tag":3572,"props":3637,"children":3638},{"class":3574,"line":116},[3639,3644,3649],{"type":603,"tag":3572,"props":3640,"children":3641},{"style":3604},[3642],{"type":608,"value":3643},"  --speculative-model",{"type":603,"tag":3572,"props":3645,"children":3646},{"style":3585},[3647],{"type":608,"value":3648}," deepseek-ai/DeepSeek-V4-Flash-DSpark-Draft",{"type":603,"tag":3572,"props":3650,"children":3651},{"style":3604},[3652],{"type":608,"value":3617},{"type":603,"tag":3572,"props":3654,"children":3655},{"class":3574,"line":117},[3656,3661],{"type":603,"tag":3572,"props":3657,"children":3658},{"style":3604},[3659],{"type":608,"value":3660},"  --num-speculative-tokens",{"type":603,"tag":3572,"props":3662,"children":3664},{"style":3663},"--shiki-default:#4C9A91",[3665],{"type":608,"value":3666}," 8\n",{"type":603,"tag":647,"props":3668,"children":3670},{"id":3669},"驗測規劃",[3671],{"type":608,"value":3669},{"type":603,"tag":604,"props":3673,"children":3674},{},[3675],{"type":608,"value":3676},"部署後建議以 DeepSpec 內附的 HumanEval 與 MATH500 腳本驗證接受率是否落在論文基準範圍（比 Eagle3 提升 26.7–30.9%）。生產環境需同步監控 P50/P99 TTFT（首 token 延遲）與每秒 output token 數 (TPS) ，確認吞吐量提升與延遲 SLA 同步達標。",{"type":603,"tag":647,"props":3678,"children":3680},{"id":3679},"常見陷阱",[3681],{"type":608,"value":3679},{"type":603,"tag":1262,"props":3683,"children":3684},{},[3685,3690,3695],{"type":603,"tag":839,"props":3686,"children":3687},{},[3688],{"type":608,"value":3689},"草稿頭與基礎模型版本必須嚴格對齊——混用不同 checkpoint 版本會導致接受率暴跌至 Eagle3 基線以下",{"type":603,"tag":839,"props":3691,"children":3692},{},[3693],{"type":608,"value":3694},"硬體感知排程器預設為 A100/H100 調校，在 V100 或消費級 GPU 上需重新調整 batch size 上限",{"type":603,"tag":839,"props":3696,"children":3697},{},[3698],{"type":608,"value":3699},"DeepSpec 訓練目前僅提供 Gemma 與 Qwen 的配置範例；其他模型系列需自行撰寫草稿頭訓練腳本",{"type":603,"tag":647,"props":3701,"children":3703},{"id":3702},"上線檢核清單",[3704],{"type":608,"value":3702},{"type":603,"tag":1262,"props":3706,"children":3707},{},[3708,3713,3718],{"type":603,"tag":839,"props":3709,"children":3710},{},[3711],{"type":608,"value":3712},"觀測：接受 token 率 (per-request) 、草稿批次長度分布、GPU 利用率熱圖",{"type":603,"tag":839,"props":3714,"children":3715},{},[3716],{"type":608,"value":3717},"成本：草稿頭推理增量記憶體（rank 256 低秩頭約 +2–4 GB VRAM per GPU）、自訓草稿頭需額外算力預算",{"type":603,"tag":839,"props":3719,"children":3720},{},[3721],{"type":608,"value":3722},"風險：跨 checkpoint 版本的草稿頭相容性、高並發下動態排程的尾延遲抖動 (P99)",{"type":603,"tag":3724,"props":3725,"children":3726},"style",{},[3727],{"type":608,"value":3728},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":429,"searchDepth":610,"depth":610,"links":3730},[],{"data":3732,"body":3733,"excerpt":-1,"toc":3982},{"title":429,"description":429},{"type":600,"children":3734},[3735,3739,3752,3758,3925,3929,3934,3938,3956,3960,3978],{"type":603,"tag":647,"props":3736,"children":3737},{"id":3547},[3738],{"type":608,"value":3547},{"type":603,"tag":604,"props":3740,"children":3741},{},[3742,3744,3750],{"type":608,"value":3743},"驗證任何二手或改裝 GPU 真偽，需要：GPU-Z（免費，Windows）、HWiNFO64（免費，Windows），以及一台已知正常的 PCIe x16 插槽主機板。Linux 用戶可用 ",{"type":603,"tag":3045,"props":3745,"children":3747},{"className":3746},[],[3748],{"type":608,"value":3749},"nvidia-smi",{"type":608,"value":3751}," 做初步核查。",{"type":603,"tag":647,"props":3753,"children":3755},{"id":3754},"最小-poc真偽驗證",[3756],{"type":608,"value":3757},"最小 PoC（真偽驗證）",{"type":603,"tag":3562,"props":3759,"children":3761},{"className":3564,"code":3760,"language":3566,"meta":429,"style":429},"# GPU-Z 驗證清單（正品 RTX 4090 預期值）\n# VRAM Size: 24576 MB（48GB 改裝版若為真：49152 MB）\n# Memory Type: GDDR6X\n# Bus Width: 384-bit\n# BIOS Version: 符合 NVIDIA 官方格式（外洩版通常含異常字串）\n\n# HWiNFO64 確認\n# Memory Clock: ~1313 MHz（正品 4090 有效 21 Gbps）\n# Memory Channels: 12（顯示 24 且 BIOS 非官方 → 高度可疑）\n\n# llama.cpp 載入測試（確認實際可用 VRAM）\n./llama-server -m model.gguf --n-gpu-layers 99 -v 2>&1 | grep \"GPU mem\"\n",[3762],{"type":603,"tag":3045,"props":3763,"children":3764},{"__ignoreMap":429},[3765,3774,3782,3790,3798,3806,3816,3825,3834,3843,3851,3860],{"type":603,"tag":3572,"props":3766,"children":3767},{"class":3574,"line":3575},[3768],{"type":603,"tag":3572,"props":3769,"children":3771},{"style":3770},"--shiki-default:#758575DD",[3772],{"type":608,"value":3773},"# GPU-Z 驗證清單（正品 RTX 4090 預期值）\n",{"type":603,"tag":3572,"props":3775,"children":3776},{"class":3574,"line":610},[3777],{"type":603,"tag":3572,"props":3778,"children":3779},{"style":3770},[3780],{"type":608,"value":3781},"# VRAM Size: 24576 MB（48GB 改裝版若為真：49152 MB）\n",{"type":603,"tag":3572,"props":3783,"children":3784},{"class":3574,"line":3620},[3785],{"type":603,"tag":3572,"props":3786,"children":3787},{"style":3770},[3788],{"type":608,"value":3789},"# Memory Type: GDDR6X\n",{"type":603,"tag":3572,"props":3791,"children":3792},{"class":3574,"line":116},[3793],{"type":603,"tag":3572,"props":3794,"children":3795},{"style":3770},[3796],{"type":608,"value":3797},"# Bus Width: 384-bit\n",{"type":603,"tag":3572,"props":3799,"children":3800},{"class":3574,"line":117},[3801],{"type":603,"tag":3572,"props":3802,"children":3803},{"style":3770},[3804],{"type":608,"value":3805},"# BIOS Version: 符合 NVIDIA 官方格式（外洩版通常含異常字串）\n",{"type":603,"tag":3572,"props":3807,"children":3809},{"class":3574,"line":3808},6,[3810],{"type":603,"tag":3572,"props":3811,"children":3813},{"emptyLinePlaceholder":3812},true,[3814],{"type":608,"value":3815},"\n",{"type":603,"tag":3572,"props":3817,"children":3819},{"class":3574,"line":3818},7,[3820],{"type":603,"tag":3572,"props":3821,"children":3822},{"style":3770},[3823],{"type":608,"value":3824},"# HWiNFO64 確認\n",{"type":603,"tag":3572,"props":3826,"children":3828},{"class":3574,"line":3827},8,[3829],{"type":603,"tag":3572,"props":3830,"children":3831},{"style":3770},[3832],{"type":608,"value":3833},"# Memory Clock: ~1313 MHz（正品 4090 有效 21 Gbps）\n",{"type":603,"tag":3572,"props":3835,"children":3837},{"class":3574,"line":3836},9,[3838],{"type":603,"tag":3572,"props":3839,"children":3840},{"style":3770},[3841],{"type":608,"value":3842},"# Memory Channels: 12（顯示 24 且 BIOS 非官方 → 高度可疑）\n",{"type":603,"tag":3572,"props":3844,"children":3846},{"class":3574,"line":3845},10,[3847],{"type":603,"tag":3572,"props":3848,"children":3849},{"emptyLinePlaceholder":3812},[3850],{"type":608,"value":3815},{"type":603,"tag":3572,"props":3852,"children":3854},{"class":3574,"line":3853},11,[3855],{"type":603,"tag":3572,"props":3856,"children":3857},{"style":3770},[3858],{"type":608,"value":3859},"# llama.cpp 載入測試（確認實際可用 VRAM）\n",{"type":603,"tag":3572,"props":3861,"children":3863},{"class":3574,"line":3862},12,[3864,3869,3873,3878,3883,3888,3893,3899,3904,3909,3915,3920],{"type":603,"tag":3572,"props":3865,"children":3866},{"style":3579},[3867],{"type":608,"value":3868},"./llama-server",{"type":603,"tag":3572,"props":3870,"children":3871},{"style":3604},[3872],{"type":608,"value":3607},{"type":603,"tag":3572,"props":3874,"children":3875},{"style":3585},[3876],{"type":608,"value":3877}," model.gguf",{"type":603,"tag":3572,"props":3879,"children":3880},{"style":3604},[3881],{"type":608,"value":3882}," --n-gpu-layers",{"type":603,"tag":3572,"props":3884,"children":3885},{"style":3663},[3886],{"type":608,"value":3887}," 99",{"type":603,"tag":3572,"props":3889,"children":3890},{"style":3604},[3891],{"type":608,"value":3892}," -v",{"type":603,"tag":3572,"props":3894,"children":3896},{"style":3895},"--shiki-default:#CB7676",[3897],{"type":608,"value":3898}," 2>&1",{"type":603,"tag":3572,"props":3900,"children":3901},{"style":3895},[3902],{"type":608,"value":3903}," |",{"type":603,"tag":3572,"props":3905,"children":3906},{"style":3579},[3907],{"type":608,"value":3908}," grep",{"type":603,"tag":3572,"props":3910,"children":3912},{"style":3911},"--shiki-default:#C98A7D77",[3913],{"type":608,"value":3914}," \"",{"type":603,"tag":3572,"props":3916,"children":3917},{"style":3585},[3918],{"type":608,"value":3919},"GPU mem",{"type":603,"tag":3572,"props":3921,"children":3922},{"style":3911},[3923],{"type":608,"value":3924},"\"\n",{"type":603,"tag":647,"props":3926,"children":3927},{"id":3669},[3928],{"type":608,"value":3669},{"type":603,"tag":604,"props":3930,"children":3931},{},[3932],{"type":608,"value":3933},"確認 BIOS 版本格式是否符合官方規則；用 llama.cpp 載入已知大小模型（如 34B Q4），觀察 VRAM 使用量是否與宣稱容量一致；對比 decode 速度 (tokens/s) 是否與同規格正品 4090 相當。",{"type":603,"tag":647,"props":3935,"children":3936},{"id":3679},[3937],{"type":608,"value":3679},{"type":603,"tag":1262,"props":3939,"children":3940},{},[3941,3946,3951],{"type":603,"tag":839,"props":3942,"children":3943},{},[3944],{"type":608,"value":3945},"GPU-Z 的 VRAM 大小可能被外洩 BIOS 欺騙——需同時核對頻率與通道數交叉驗證",{"type":603,"tag":839,"props":3947,"children":3948},{},[3949],{"type":608,"value":3950},"部分假卡輕負載下正常，高溫高負載後才崩潰；測試需跑完整推論工作負載",{"type":603,"tag":839,"props":3952,"children":3953},{},[3954],{"type":608,"value":3955},"雷射重蝕的晶片標記肉眼幾乎完美，需放大鏡才能發現邊緣加工痕跡",{"type":603,"tag":647,"props":3957,"children":3958},{"id":3702},[3959],{"type":608,"value":3702},{"type":603,"tag":1262,"props":3961,"children":3962},{},[3963,3968,3973],{"type":603,"tag":839,"props":3964,"children":3965},{},[3966],{"type":608,"value":3967},"觀測：GPU-Z BIOS 版本格式、HWiNFO 記憶體頻率與通道數、llama.cpp 實測 VRAM 可用量",{"type":603,"tag":839,"props":3969,"children":3970},{},[3971],{"type":608,"value":3972},"成本：驗證工具均免費；需物理拆機時建議委託有信譽的維修店",{"type":603,"tag":839,"props":3974,"children":3975},{},[3976],{"type":608,"value":3977},"風險：改裝卡無原廠保固，故障後只能自費維修或直接報廢；15–20% 失效率下建議只在有備援方案時使用",{"type":603,"tag":3724,"props":3979,"children":3980},{},[3981],{"type":608,"value":3728},{"title":429,"searchDepth":610,"depth":610,"links":3983},[]]