Knowledge
Directional only- Gemma 4 E4B
- 67.4
- GLM-5.2
- 59.6
- Weighted basis
- 2 vs 2 rows
- Reading
- Directional only
Model comparison
Updated July 31, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
GLM-5.2 has the higher public score estimate, 62.94 versus 42.04, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.
1 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
Prompts that approach the documented context limit
GLM-5.2
GLM-5.2 has the larger documented context window.
Confidence: documented
Code generation, repair, and software-engineering tasks
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
Tool use, computer use, and multi-step task completion
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. Gemma 4 E4B does not fit this workload in one request. GLM-5.2 has no published cached-input rate, so cached tokens use its listed input rate. Gemma 4 E4B has no comparable published API token rate.
Confidence: rate-fallback
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
1 category uses different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Each row states whether both averages use the same weighted benchmark set. Directional and not-comparable rows remain visible, but they never receive a winner in this template.
| Category | Gemma 4 E4B | GLM-5.2 | Weighted basis | Reading |
|---|---|---|---|---|
| Knowledge | 67.4 | 59.6 | Directional only2 vs 2 rows | Directional only |
| Agentic | Not measured | 81.0 | Not comparable0 vs 1 rows | Not comparable |
| Coding | Not measured | 62.1 | Not comparable0 vs 1 rows | Not comparable |
| Reasoning | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Math | Not measured | 95.9 | Not comparable0 vs 2 rows | Not comparable |
| Multilingual | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Multimodal | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Instruction following | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.
GPQA
Knowledge
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
1K fresh input + 500 output tokens
Gemma 4 E4B has no comparable published API token rate.
50K fresh input + 3K output tokens
Gemma 4 E4B has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
Gemma 4 E4B does not fit this workload in one request. GLM-5.2 has no published cached-input rate, so cached tokens use its listed input rate. Gemma 4 E4B has no comparable published API token rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
Gemma 4 E4B
GLM-5.2
1M
Gemma 4 E4B
Not sourced
GLM-5.2
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Gemma 4 E4B
No comparable hosted API rate
GLM-5.2
Not published
Gemma 4 E4B
text, image, audio, video
Google Gemma 4 model documentationGLM-5.2
Not sourced
Gemma 4 E4B
GLM-5.2
Not sourced
Gemma 4 E4B
Open Weights · open weights
Google gemma-4-E4B model cardGLM-5.2
Not sourced
Gemma 4 E4B
Reasoning
GLM-5.2
Reasoning
Gemma 4 E4B
Open Weight
GLM-5.2
Open Weight
Gemma 4 E4B
Open Weight
GLM-5.2
Open Weight
Gemma 4 E4B
2026-04-02
GLM-5.2
2026-06-16
Run the same representative tasks against both endpoints before changing production traffic.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
SWE-bench Pro
Not directly comparable
NL2Repo
Not directly comparable
Terminal-Bench 2.0
Not directly comparable
ProgramBench
Not directly comparable
cursorBench32
Not directly comparable
CritPt
Not directly comparable
GPQA
GLM-5.2 leads this result
MMLU-Pro
Not directly comparable
GPQA-D
Not directly comparable
HLE
Not directly comparable
HLE w/o tools
Not directly comparable
GLM-5.2 has the higher public score estimate, 62.94 versus 42.04, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
The published evidence does not provide a shared weighted coding basis for both models, so BenchLM does not name a coding winner.
The published evidence does not provide a shared weighted agentic tasks basis for both models, so BenchLM does not name a agentic tasks winner.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
GLM-5.2 has the larger documented context window: 1M, compared with 128K.
Last updated July 31, 2026
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.