Models / glm-5-3-flash
GLM-5.3 Flash
Z.ai's model, with open weights. Forcebench has run it in 5 configurations on the API and Local boards, plus 6 on the lite subset. API is models reached through a hosted service; Local, models served on Forcebench’s own hardware.
On the API board
Models reached through a hosted service. GLM-5.3 Flash is ranked by its one configuration: the 17th-highest score of 26 models, not clearly different from 5 other models. Scores are within 3 attempts (c@3) with 95% intervals; each configuration is compared with the highest-scoring one by whether their 95% intervals overlap. Every configuration on the board → Cost and speed →
| Configuration | Rank all configs | Within 3 attempts c@3 · 95% CI | Tokens mean · median · p90 | No answer | Latency median per task, every attempt counted | Cost per task | Cost per solved task |
|---|---|---|---|---|---|---|---|
| OpenRouter · FP8 · highhighest score | 30 | 65%95% CI 60–69 | 3.5k1.1k · 9k | 1% | 30 s | $0.0043 | $0.0066 |
- 95% interval
- API board median
Show the numbers
| Suite | c@3 95% CI | API median | Tasks |
|---|---|---|---|
| Apex | 90%95% CI 70–97 | 90% | 20 |
| Salesforce APIs | 72%95% CI 49–88 | 72% | 18 |
| CI/CD | 82%95% CI 59–94 | 88% | 17 |
| Salesforce CLI | 75%95% CI 53–89 | 90% | 20 |
| Salesforce docs | 12%95% CI 3–34 | 29% | 17 |
| fflib Enterprise Patterns | 39%95% CI 20–61 | 61% | 18 |
| Flow | 22%95% CI 9–45 | 69% | 18 |
| Governor limits & pushback | 79%95% CI 57–91 | 89% | 19 |
| Lightning Web Components | 94%95% CI 74–99 | 100% | 18 |
| Nonprofit Success Pack | 67%95% CI 44–84 | 81% | 18 |
| Packaging | 44%95% CI 25–66 | 69% | 18 |
| Permissions & access | 80%95% CI 55–93 | 87% | 15 |
| Scratch org definitions | 44%95% CI 25–66 | 50% | 18 |
| SOQL | 90%95% CI 70–97 | 100% | 20 |
| Trigger Actions Framework | 78%95% CI 55–91 | 86% | 18 |
On the Local board
Models served on Forcebench’s own hardware. GLM-5.3 Flash is ranked by the highest-scoring of its 4 configurations: the second-highest score of 9 models, not clearly different from 2 other models. Scores are within 3 attempts (c@3) with 95% intervals; each configuration is compared with the highest-scoring one by whether their 95% intervals overlap. Every configuration on the board →
- 95% interval
Show the numbers
| Configuration | Rank all configs | Within 3 attempts c@3 · 95% CI | Against the highest by 95% interval overlap | Tokens mean · median · p90 | No answer | Latency median per task, every attempt counted |
|---|---|---|---|---|---|---|
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · highhighest score | 3 | 64%95% CI 59–68 | — | 3.4k1.1k · 10k | 2% | 86 s |
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · low | 4 | 60%95% CI 55–66 | not clearly different | 733401 · 1.9k | 0% | 36 s |
| EXL3 4.0bpw experts, 4-bit dense · TensorFold · high · 2× NVIDIA DGX Spark (GB10, 128 GB each) | 6 | 54%95% CI 49–59 | not clearly different | 4k1.2k · 10k | 2% | 58 s |
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · thinking off | 10 | 50%95% CI 44–55 | clearly lower | 2.3k644 · 4.4k | 0% | 62 s |
Latency depends on the hardware: compare it only between configurations on the same hardware.
- 95% interval
- Local board median
Show the numbers
| Suite | c@3 95% CI | Local median | Tasks |
|---|---|---|---|
| Apex | 90%95% CI 70–97 | 70% | 20 |
| Salesforce APIs | 56%95% CI 34–75 | 44% | 18 |
| CI/CD | 82%95% CI 59–94 | 53% | 17 |
| Salesforce CLI | 85%95% CI 64–95 | 45% | 20 |
| Salesforce docs | 12%95% CI 3–34 | 12% | 17 |
| fflib Enterprise Patterns | 33%95% CI 16–56 | 17% | 18 |
| Flow | 33%95% CI 16–56 | 17% | 18 |
| Governor limits & pushback | 89%95% CI 69–97 | 84% | 19 |
| Lightning Web Components | 94%95% CI 74–99 | 89% | 18 |
| Nonprofit Success Pack | 83%95% CI 61–94 | 61% | 18 |
| Packaging | 39%95% CI 20–61 | 39% | 18 |
| Permissions & access | 67%95% CI 42–85 | 60% | 15 |
| Scratch org definitions | 39%95% CI 20–61 | 17% | 18 |
| SOQL | 95%95% CI 76–99 | 90% | 20 |
| Trigger Actions Framework | 56%95% CI 34–75 | 44% | 18 |
By reasoning effort
The same configuration at several efforts, each against its lowest reasoning effort on the same tasks (a paired 95% interval), and charted against the effort tier and against the output tokens it costs. These scores are pass@1, the first answer alone: a paired comparison needs both efforts' answers to the same tasks, and not every effort has had its retries. Lite-subset sweeps (4 tasks per suite) are never plotted with the full benchmark. The effort study has every model.
| Configuration · effort · full benchmark | pass@1 95% CI | Against the lowest reasoning effort same tasks, paired | Tokens |
|---|---|---|---|
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · thinking off | 34%95% CI 29–39 | no clear difference (±0 pts, 95% CI −6 pts to +5 pts); this data can't rule out a change of up to 6 points | 2.3k |
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · lowbaseline | 34%95% CI 29–40 | — | 733 |
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · high | 43%95% CI 38–48 | clearly higher (+9 pts, 95% CI +3 pts to +15 pts) | 3.4k |
Show the numbers
| Model | Effort (tier) | pass@1 | 95% CI | Tasks | No answer | Tokens: mean | median | Latency: median per answer |
|---|---|---|---|---|---|---|---|---|
| GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense | thinking off | 34% | 29–39 | 272 | 0% | 2.3k | 644 | 38 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense | low | 34% | 29–40 | 272 | 0% | 733 | 401 | 23 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense | high | 43% | 38–48 | 272 | 2% | 3.4k | 1.1k | 64 s |
| Configuration · effort · lite subset | pass@1 95% CI | Against the lowest reasoning effort same tasks, paired | Tokens |
|---|---|---|---|
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · thinking off | 33%95% CI 23–43 | no clear difference (+1 pt, 95% CI −10 pts to +13 pts); this data can't rule out a change of up to 13 points | 2.6k |
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · lowbaseline | 32%95% CI 23–40 | — | 710 |
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · max | 35%95% CI 25–45 | no clear difference (+3 pts, 95% CI −8 pts to +15 pts); this data can't rule out a change of up to 15 points | 15k |
| EXL3 4.0bpw experts, 4-bit dense · TensorFold · thinking off | 23%95% CI 15–32 | no clear difference (−4 pts, 95% CI −13 pts to +7 pts); this data can't rule out a change of up to 13 points | 3k |
| EXL3 4.0bpw experts, 4-bit dense · TensorFold · lowbaseline | 27%95% CI 17–37 | — | 1.5k |
| EXL3 4.0bpw experts, 4-bit dense · TensorFold · max | 33%95% CI 25–43 | no clear difference (+6 pts, 95% CI −3 pts to +17 pts); this data can't rule out a change of up to 17 points | 16k |
- GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense
- GLM-5.3 Flash · EXL3 4.0bpw experts, 4-bit dense
Show the numbers
| Model | Effort (tier) | pass@1 | 95% CI | Tasks | No answer | Tokens: mean | median | Reasoning tokens | Latency: median per answer |
|---|---|---|---|---|---|---|---|---|---|
| GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense | thinking off | 33% | 23–43 | 60 | 0% | 2.6k | 682 | — | 39 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense | low | 32% | 23–40 | 60 | 0% | 710 | 442 | — | 25 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense | max · vendor default | 35% | 25–45 | 60 | 27% | 15k | 12k | — | 688 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, 4-bit dense | thinking off | 23% | 15–32 | 60 | 0% | 3k | 860 | — | 37 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, 4-bit dense | low | 27% | 17–37 | 60 | 2% | 1.5k | 446 | 450 | 17 s |
| GLM-5.3 Flash · EXL3 4.0bpw experts, 4-bit dense | max · vendor default | 33% | 25–43 | 60 | 28% | 16k | 13k | 6.5k | 570 s |
- GLM-5.3 Flash · EXL3 4.0bpw experts, FP8 dense
- GLM-5.3 Flash · EXL3 4.0bpw experts, 4-bit dense
By quantisation
The same effort in different quantisations, each against the highest-precision one on the same tasks (a paired 95% interval), on pass@1, the first answer alone. Where the engine changes too, a difference can't be put down to quantisation alone. The quantisation study has every model.
- 95% interval
Show the numbers
| Build | pass@1 | 95% CI | Tokens |
|---|---|---|---|
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 | 43% | 38–48 | 3.4k |
| EXL3 4.0bpw experts, 4-bit dense · TensorFold · 2× NVIDIA DGX Spark (GB10, 128 GB each) | 37% | 32–42 | 4k |
| Quantisation · engine · high | pass@1 95% CI | Against EXL3 4.0bpw experts, FP8 dense same tasks, paired | Tokens |
|---|---|---|---|
| EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3reference | 43%95% CI 38–48 | — | 3.4k |
| EXL3 4.0bpw experts, 4-bit dense · TensorFold · 2× NVIDIA DGX Spark (GB10, 128 GB each) | 37%95% CI 32–42 | clearly lower (−6 pts, 95% CI −12 pts to −0.7 pts) | 4k |
In the studies
- Reasoning effort: its score against effort and against output tokens.
- Max effort: what its max effort did against the effort below it.
- Quantisation: its quantisations side by side.
- Local vs API: where it lands among the configurations of both boards.
- Pushback: whether it pushed back on requests that break at scale.
Private evaluations
Want this for your team?
Azul Labs runs Forcebench privately for two kinds of Salesforce team.
Choosing a model to run yourself?
A private benchmark of your shortlist
Open-weight models at the quantisations and reasoning efforts you could run on infrastructure you control, tested on your kind of Salesforce work, with a written recommendation.
- Private tasks written from your work only ever run on local models; they are never sent to an API.
- Re-testing after any change of model, quantisation or engine is available.
- Typical turnaround is 2–3 weeks; large models take about a day of machine time per configuration.
Building or buying a Salesforce AI tool?
A private evaluation of your tool
Your tool on held-out tasks it has never seen, against API baselines (models reached through a hosted service) and Local ones (served on Forcebench’s own hardware), with a written report on where it holds up and where it fails.
- It can start as a smaller pilot, about 30 held-out tasks with your tool against two baselines, before a full evaluation.
- Repeat evaluations after your releases are available.
- Typical turnaround is 2–3 weeks.
Fixed fee, quoted up front. The quote depends on the number of tasks and the number of models, tools or configurations tested.
Or email leo@azl.au · azl.au