Pass@N

Pass rate

Tasks solved / tasks in scope, up to 2 attempts (strict per-set denominator).

Formula: (tasks_passed_attempt_1 + tasks_passed_attempt_2_only) / task_set_size

Includes unattempted tasks as failures. Scope-aware; reflects active filters (set, category, difficulty). Primary ranking metric.

50.0%
Tasks pass 32/64
1st: 28 2nd: 4 Failed: 32
Avg cost / task

Avg cost / task

Average LLM cost per distinct benchmark task in USD.

Formula: SUM(cost_usd) / COUNT(DISTINCT task_id) across all the model's results in scope.

Use to compare operating cost across models with similar pass rates. Does not account for quality. Combine with $/Pass for a cost-efficiency view.

$0.02
Latency p50

Latency p50

Median per-task wall time (LLM call + compile + test), in milliseconds.

Formula: 50th percentile of per-task duration_ms: LLM latency + compile time + test time.

Use p50 for a typical-case latency expectation. Unaffected by outlier slow tasks.

2m 6s
Avg score

Avg attempt score

Mean per-attempt score on a 0–100 point scale (partial credit). Drill-down only.

Formula: Mean of attempt scores across all results rows: SUM(score) / COUNT(*) over the results table. Each attempt earns 0–100 points based on compile + test outcomes.

Drill-down companion to pass_at_n. Rewards partial credit but not directly comparable to pass rate; use for within-model analysis.

26.9 / 100
All-runs pass rate

All-runs pass rate

Fraction of tasks the model solved in every single run (strict consistency, also written pass^n).

Formula: tasks where ALL runs produced a passing result / tasks_attempted_distinct

Measures reliability under repetition. High value means the model is unlikely to regress on a re-run, important for CI and production use. Formal name in the literature: pass^n.

25.0%
$/Pass

$/Pass

Total cost divided by number of distinct tasks passed. Lower is better.

Formula: SUM(cost_usd) / tasks_passed_distinct across all runs.

Best single cost-efficiency metric. Penalises expensive models that pass few tasks and rewards cheap models with high pass rates.

$0.0337
Latency p95

Latency p95

95th-percentile per-task wall time. Captures tail latency.

Formula: 95th percentile of per-task duration_ms across all tasks in all runs.

Use p95 to understand worst-case latency. A low p95 means the model rarely stalls, relevant for automated pipelines with timeouts.

6m 9s

Overview

DeepSeek V4 Pro has run on 3 occasions, attempting 64 tasks with an average score of 26.9 / 100.

Settings

Generation parameters used across this model's runs. "varies" indicates the value differed between runs.

Temperature
varies
Thinking budget
varies
Avg tokens / run (input + output)
465,130
Consistency
59.4%

History

1
2
3
3 runs · oldest 9d ago · latest 10d ago

Cost

meanp95

Failure modes

  • AL0104 632 Syntax error, ')' expected view all →
  • AL0000 226 App generation failed view all →
  • AL0111 150 Semicolon expected. Add a semicolon (;) to terminate the statement. view all →
  • AL0107 109 Syntax error, identifier expected. Provide a valid name (letters, digits, and underscores only). view all →
  • AL0198 108 Expected one of the application object keywords (table, tableextension, page, pageextension, pagecustomization, profile, profileextension, codeunit, report, reportextension, xmlport, query, controladdin, dotnet, enum, enumextension, interface, permissionset, permissionsetextension, entitlement) view all →
  • AL0118 105 The name 'Code' does not exist in the current context. view all →
  • AL0132 99 'Text' does not contain a definition for 'Length' view all →
  • AL0133 48 Argument 2: cannot convert from 'Integer' to 'Text' view all →
  • AL0124 40 The property '"Preferred Contact Method"' cannot be used in this context. Verify the property is available for the current object type. view all →
  • AL0114 36 Syntax error, integer literal expected. Provide a numeric value (e.g., 0, 1, 42). view all →

Shortcomings

AL concepts DeepSeek V4 Pro struggles with. Click a row for description, correct pattern, and observed error codes.

Shortcomings analysis queued

Queued for analysis. This section will populate once the run is processed.

Recent runs

Runs
StartedRunModelTasksScoreCostDurationStatus
9d ago88d9b561-ee9…26/6427.9 / 100$0.354h 27mcompleted
10d agod29122fc-997…26/6429.0 / 100$0.344h 38mcompleted
10d ago0a7fca96-9d4…21/6423.9 / 100$0.394h 45mcompleted

See all 3 runs →

Methodology

Pass rate counts unattempted tasks as failures (strict denominator). Avg score is the mean of every attempt the model produced — failed first tries that triggered a retry contribute one observation each, pulling the mean down. See the about page for the full breakdown and unit conventions.