Baidu Unveils ERNIE 5.5 Flash Preview With 280B Total and 14B Active Parameters
By Mr.Xu Community Post
Published:
Summary:Baidu has introduced ERNIE 5.5 Flash Preview, a sparse model with 280B total parameters and roughly 14B active parameters per token. A community summary of an agentic-coding index places Terminal-Bench v4.0 and DeepSWE v1.1 at 31% of the aggregate weight, suggesting particularly strong terminal-operation and software-engineering results. The information remains incomplete: model weights, licensing, supported inference runtimes, context length, quantization quality, and end-to-end serving throug
Core Release
Baidu's ERNIE 5.5 Flash Preview is presented as a sparse model with 280B total parameters and about 14B active parameters per token, or roughly 5% parameter activation. That profile is consistent with a mixture-of-experts design: each token traverses only a subset of experts rather than the entire model. If the final architecture uses MoE, the intended benefit is lower per-token matrix-multiplication cost while the larger parameter pool provides room for specialized capabilities.
The available community material does not disclose the number of experts, routing granularity, shared-expert design, or attention implementation. The 14B-active figure therefore cannot be converted directly into throughput. MoE serving costs also include routing overhead, resident expert weights, all-to-all communication, and poor utilization at small batch sizes.
Coding and Agent Performance
A community leaderboard screenshot shows ERNIE 5.5 Flash Preview performing strongly on an aggregate “Agentic Coding” index. The index consists entirely of coding and software-engineering benchmarks: Terminal-Bench v4.0 contributes 16%, DeepSWE v1.1 15%, FrontierCode 2.0 11%, Code Migration 9%, Terminal-Bench v2.1 8.5%, SRE-Bench 8%, SWE-bench Pro 7.5%, Code Arena Elo 6.5%, Program-Bench 6%, Vibe Code Bench v1.1 5.5%, SciCode 4%, and LiveCodeBench v6 3%.
Terminal-Bench v4.0 and DeepSWE v1.1 alone account for 31%, making terminal operation and repository-level problem solving especially influential in the result. Code generation, repository migration, and SRE tasks add other dimensions. However, the post does not provide per-benchmark scores, confidence intervals, repeated-run statistics, or failure traces, so the aggregate ranking cannot be independently reconstructed.
How to Interpret the Benchmark
This is a coding-specific index, not a general agent benchmark, and it should not be treated as a direct measure of end-to-end software-engineering reliability. It combines terminal tasks, real-repository issue resolution, human preference, and contest-style programming. Those measures are complementary but not interchangeable, making the aggregate score more useful as a screening signal than as a complete capability model.
Aggregate leaderboards can also be affected by contamination, leakage, and benchmark-specific optimization. The screenshot does not specify evaluation dates, prompt templates, sampling counts, tool configuration, pass@k calculation, or raw outputs. For terminal agents, retry limits, repository history, execution timeouts, and permission boundaries can materially change the final score.
Engineering Trade-offs
Parameter efficiency is not deployment efficiency. At 280B parameters, even 4-bit weights require roughly 140GB before scales, metadata, KV Cache, and runtime overhead. An 8-bit deployment would need about 280GB. A single workstation GPU is therefore not a practical target; realistic deployments would require multi-GPU expert parallelism, cross-node sharding, or a hosted service.
MoE shifts the bottleneck toward communication. In a fine-grained expert architecture, each token goes through dispatch, expert computation, and combine phases. All-to-All traffic can dominate latency across nodes. Increasing expert parallelism provides more weight capacity but also raises network pressure. Batch size, expert capacity factors, routing imbalance, and context length all affect end-to-end performance.
Fewer active parameters do not mean less memory. The model may compute only 14B active parameters per token, but it still has to store 280B weights. Memory capacity, bandwidth, and interconnect topology can therefore become bottlenecks before active FLOPs do. Long contexts further increase KV Cache usage.
Deployment Guidance
- Wait for the official model card, license, and API documentation. Confirm whether weights are available, whether commercial use is permitted, and whether the model supports function calling, tool use, and structured output.
- Reproduce three workload classes on an internal codebase: terminal operation, repository-level issue fixing, and code migration. Preserve prompts, container images, tool permissions, and sampling parameters.
- Measure time to first token, inter-token latency, concurrent throughput, expert load balance, and the share of time spent on inter-node communication. Do not compare active parameter counts alone.
- Test FP16 or BF16 against FP8 and INT4 variants, checking for regressions in code correctness, tool-call format adherence, and long-context stability.
- Compare the model with contemporaneous dense models, other sparse models, and established coding-agent baselines. Report pass@k, task success rate, and cost per completed task rather than relying on one aggregate score.
The defensible takeaway is that ERNIE 5.5 Flash Preview demonstrates the potential of handling demanding coding-agent workloads with about 14B active parameters. Its real-world value still depends on weight access, inference-framework support, multi-node efficiency, and independent reproduction.
— END —Source: Reddit r/LocalLLaMA (2026-11-12)
Tags: #Baidu #ERNIE 5.5 #Sparse MoE #Coding Agents #Model Evaluation
Editorial & Fact-Checking Note: This article is compiled from primary research, official release documentation, and source papers by the ZICQ Newsroom pipeline with automated entity verification and human editorial review. If you notice any technical inaccuracy, please submit a correction via our corrections policy or email our editorial desk directly.
Community Comments