Qwen3.6 35B-A3B

Qwen's model, with open weights. Forcebench has run it in 1 configuration on the Local board, plus 1 on the lite subset. API is models reached through a hosted service; Local, models served on Forcebench’s own hardware.

On the Local board

Models served on Forcebench’s own hardware. Qwen3.6 35B-A3B is ranked by its one configuration: the ninth-highest score of 9 models, not clearly different from 3 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 →

34%
within 3 attempts (c@3), 95% CI 29–39 · thinking on · ninth-highest score of 9 models, not clearly different from 3 other models
6.1k
output tokens per task · median 4.6k, p90 11k
71 s
median per task, every attempt counted, on 1× NVIDIA GeForce RTX 5090 (32 GB) · 90th percentile 257 s
2%
no answer within the 32,768-token budget
Every configuration of Qwen3.6 35B-A3B on the Local board
ConfigurationRank all configsWithin 3 attempts c@3 · 95% CITokens mean · median · p90No answerLatency median per task, every attempt counted
NVFP4 · vLLM · thinking on · 1× NVIDIA GeForce RTX 5090 (32 GB)highest score20
34%95% CI 29–39
6.1k4.6k · 11k2%71 s

Latency depends on the hardware: compare it only between configurations on the same hardware.

Suites, at its highest-scoring configuration
thinking on · NVFP4 · vLLM · 1× NVIDIA GeForce RTX 5090 (32 GB): within 3 attempts (c@3) on each suite with 95% intervals, against the median of the Local board's models, each at its highest-scoring configuration.
  • 95% interval
  • Local board median
45%, 95% interval 26–66%
39%, 95% interval 20–61%
29%, 95% interval 13–53%
15%, 95% interval 5–36%
0%, 95% interval 0–18%
17%, 95% interval 6–39%
11%, 95% interval 3–33%
68%, 95% interval 46–85%
44%, 95% interval 25–66%
50%, 95% interval 29–71%
28%, 95% interval 13–51%
40%, 95% interval 20–64%
17%, 95% interval 6–39%
70%, 95% interval 48–85%
39%, 95% interval 20–61%
    Show the numbers
    Per-suite scores of Qwen3.6 35B-A3B's highest-scoring configuration on the Local board, with the board's median
    Suitec@3 95% CILocal medianTasks
    Apex
    45%95% CI 26–66
    70%20
    Salesforce APIs
    39%95% CI 20–61
    44%18
    CI/CD
    29%95% CI 13–53
    53%17
    Salesforce CLI
    15%95% CI 5–36
    45%20
    Salesforce docs
    0%95% CI 0–18
    12%17
    fflib Enterprise Patterns
    17%95% CI 6–39
    17%18
    Flow
    11%95% CI 3–33
    17%18
    Governor limits & pushback
    68%95% CI 46–85
    84%19
    Lightning Web Components
    44%95% CI 25–66
    89%18
    Nonprofit Success Pack
    50%95% CI 29–71
    61%18
    Packaging
    28%95% CI 13–51
    39%18
    Permissions & access
    40%95% CI 20–64
    60%15
    Scratch org definitions
    17%95% CI 6–39
    17%18
    SOQL
    70%95% CI 48–85
    90%20
    Trigger Actions Framework
    39%95% CI 20–61
    44%18

    In the studies

    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