BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership
BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership
  1. Home
  2. Our Tests
  3. Summary
blxbench

Test fixture

Summary

Speedhardscorer: contains_all

Latency-sensitive tasks where concise correct output matters.

How it is scored

The model receives the prompt (and optional system message). The run uses scorer contains_all with the JSON configuration below. Pass/fail and partial credit are determined entirely by that scorer against the model output; no human grading.

User prompt
Summarize in exactly 4 short bullet points:
A platform team improved release safety by introducing dead-letter queues, on-call rotations, and queue backpressure across critical services. They documented ownership, ran weekly reliability reviews, and tracked cost per request to verify impact over time.
Scorer config
{
  "expected_contains": [
    "dead-letter queues",
    "on-call rotations",
    "queue backpressure",
    "cost per request"
  ]
}
Run parameters

temperature

0

max_tokens

140

timeout (s)

120

type

scored

file

speed_hard_06.json

← PreviousSummary
|
Next →Summary

BLXBench

Community driven leaderboardPublic benchmark runner — run in your environment, share results with the community.

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope6 / 7 / 372
Latestrun_5434c2 / 7 / $0.00
TermsPrivacy