Models / muse-glimmer-30b

Muse Glimmer 30B

Meta's model, with open weights. Forcebench has run it in 1 configuration on the Local board. 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. Muse Glimmer 30B is ranked by its one configuration: the eighth-highest score of 16 models, not clearly different from 7 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 →

45%
within 3 attempts (c@3), 95% CI 40–50 · high · eighth-highest score of 16 models, not clearly different from 7 other models
4k
output tokens per task · median 3.4k, p90 7.3k
111 s
median per task, every attempt counted, on 1× NVIDIA GeForce RTX 5090 (32 GB) · 90th percentile 437 s
0%
no answer within the 32,768-token budget
Every configuration of Muse Glimmer 30B on the Local board
ConfigurationRank all configsWithin 3 attempts c@3 · 95% CITokens mean · median · p90No answerLatency median per task, every attempt counted
NVFP4 + FP8 mixed (NVIDIA ModelOpt) · vLLM · high · 1× NVIDIA GeForce RTX 5090 (32 GB)highest score16
45%95% CI 40–50
4k3.4k · 7.3k0%111 s

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

Suites, at its highest-scoring configuration
high · NVFP4 + FP8 mixed (NVIDIA ModelOpt) · 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
Apex
75%, 95% interval 53–89%
Salesforce APIs
39%, 95% interval 20–61%
CI/CD
53%, 95% interval 31–74%
Salesforce CLI
30%, 95% interval 15–52%
Salesforce docs
12%, 95% interval 3–34%
fflib Enterprise Patterns
17%, 95% interval 6–39%
Flow
22%, 95% interval 9–45%
Governor limits & pushback
84%, 95% interval 62–94%
Lightning Web Components
83%, 95% interval 61–94%
Nonprofit Success Pack
56%, 95% interval 34–75%
Packaging
22%, 95% interval 9–45%
Permissions & access
47%, 95% interval 25–70%
Scratch org definitions
11%, 95% interval 3–33%
SOQL
80%, 95% interval 58–92%
Trigger Actions Framework
39%, 95% interval 20–61%
    Show the numbers
    Per-suite scores of Muse Glimmer 30B's highest-scoring configuration on the Local board, with the board's median
    Suitec@3 95% CILocal medianTasks
    Apex
    75%95% CI 53–89
    		70%20
    Salesforce APIs
    39%95% CI 20–61
    		42%18
    CI/CD
    53%95% CI 31–74
    		44%17
    Salesforce CLI
    30%95% CI 15–52
    		38%20
    Salesforce docs
    12%95% CI 3–34
    		12%17
    fflib Enterprise Patterns
    17%95% CI 6–39
    		17%18
    Flow
    22%95% CI 9–45
    		17%18
    Governor limits & pushback
    84%95% CI 62–94
    		76%19
    Lightning Web Components
    83%95% CI 61–94
    		83%18
    Nonprofit Success Pack
    56%95% CI 34–75
    		56%18
    Packaging
    22%95% CI 9–45
    		28%18
    Permissions & access
    47%95% CI 25–70
    		57%15
    Scratch org definitions
    11%95% CI 3–33
    		11%18
    SOQL
    80%95% CI 58–92
    		85%20
    Trigger Actions Framework
    39%95% CI 20–61
    		42%18

    In the studies

    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.
    Get a private benchmarkHow it works

    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.
    Ask about an evaluationHow it works

    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