GLM-5.3-CYBERSECURITY-FP8

モデル紹介

a **CRACK** release by dealignai · Twitter @dealignai > [!IMPORTANT] > **Runtime notes** — field-tested on 8× DGX Spark GB10 by @0xMagnus (discussion): > > - **`reasoning_effort` only honors `"low"` and `"high"`.** Every other value — `off`, `medium`, `max`, unset, or an unquoted YAML `off:` (parses as boolean `false`) — falls through to `max`. There is no way to disable reasoning on this checkpoint; pass `"low"` for minimum. > - **On FP8, prefer `low` for agent / tool-loop use.** At `high`/`max` the model can spend the whole `max_tokens` budget inside ` ` and return zero answer tokens (finish=`length`); sampling params (temp 0 + rep 1.05, temp 0.7 / top-p 0.95) do not rescue it. It is budget exhaustion, not a loop. If you must run `high`/`max`, give `max_tokens ≥ 8000`. > - **Reasoning text is in `message.reasoning`**, not `message.reasoning_content`. > - **MTP:** non-functional on stock vLLM, but reported working on ciprianveg's B12X sparse-MLA vLLM fork with `--draft-attention-backend B12X_MLA_SPARSE` (+48% decode on coding prompts). > - **1M context via decode-context-parallel is closed** on `glm_moe_dsa` in vLLM today (DSA indexer `k_cache` is replicated across DCP ranks while MLA KV is sharded → `page size is not divisible by target page size and cannot be padded` for `fp8_ds_mla`). Practical TP8 H200 ceiling: ~131K w/MTP, ~160K w/o. Pipeline-parallel (PP2 × TP4) profiles fine, but the MTP draft does not implement `SupportsPP`. **This is a CYBERSECURITY-DOMAIN CRACK of GLM-5.3-FP8 — not a general-purpose uncensor.**

主な特徴

特点摘要待依据来源补齐，不凭模型名称推断能力。

制約と注意点

具体的な制約を判断する出典が不足しています。実際の性能、遅延、データ方針、ライセンス、提供期間を確認してください。

出典別料金と費用分析

料金はチャネル・地域・設定によって異なります。各チャネルの料金は個別に表示し、提供元の統一公式料金とは見なしません。

公開評価と実行設定

暂无已采集的可核验公开评分。模型未上榜不代表能力较低。

よくある質問

出典と追跡記録

许可证：mit。模型介绍与第三方评测均以原来源的具体版本和方法为准。