BANTAM FACTORY / fight card
Glob select.
Match paths against glob patterns, last pattern deciding, with a receipt per path.
Matchup completed with follow-up runs. DeepSeek Harness, Hermes, OpenCode · 2026-09-08. Original BANTAM FACTORY result retained. Task, starter, grader and local model hashes match. Run conditions ↓
BANTAM FACTORY'S LOCAL SETUP
NVIDIA RTX 4090 · 24 GB
Qwen 27B · Q4_K_P · 72,192 context tokens
What does this mean for my setup?
This run used Qwen 27B on NVIDIA RTX 4090 · 24 GB. Compare generation speed using the same model and quantization. GPU memory, CPU offload, context size and prompt caching also affect performance.
Generation speed is measured while the server produces tokens. The task clock also includes reading context, running tools and testing. A GPU speed difference does not translate directly into the same change in total task time.
Fresh prompt processing: 1,643 tok/s · 27/27 timed requests. Rates use total recorded tokens divided by total server time for each phase. Hardware is operator-confirmed; timings come from the saved server responses.
The recorded factory floor
Meet the contenders.
4 local configurations.
1 frontier reference, shown separately.
Choose any contender. Open its work.
Bars show elapsed time against the longest recorded run, not percentage of work completed. Token counters advance only when a saved response supplies them.
Recorded system comparison
Glob select
| System | Outcome | Time | Groups | Project accepted | Clean finish | Input | Output | Cached input | Fresh input | Scope |
|---|---|---|---|---|---|---|---|---|---|---|
| BANTAM FACTORY · localQwen 27B · same local model | PASS | 264.1s | 5/5 | Yes | Yes | 503,914 | 19,280 | 459,965 | 43,949 | Recorded totals |
| Codex · AstraGPT-6 Astra · native CLI | PASS | 155.8s | 5/5 | Yes | Yes | 77,389 | 4,409 | 63,104 | 14,285 | Recorded totals |
| DeepSeek HarnessQwen 27B · same local model | FAIL | 551.4s | 0/5 | No | No | 37,704 | 33,057 | 27,370 | 10,334 | Recorded totals |
| HermesQwen 27B · same local model | TIMEOUT | 600.0s | 0/5 | No | No | 349,061 | 35,930 | 326,913 | 22,148 | Measured subset |
| OpenCodeQwen 27B · same local model | TIMEOUT | 600.0s | 0/5 | No | No | 27,071 | 33,152 | 16,924 | 10,147 | Measured subset |
Qualification historyProgress includes the misses.0 local editions +
Selected qualification editions, not every development experiment. Earlier included failures are retained. These are separate attempts, not repeated trials of an unchanged system. An unrecorded task is not a failure.
Method & evidenceThe work order and run conditions.Read the method +
The recorded comparison
1 included work order: BUILD — Glob select (repeat 1). 5 systems and 5/5 recorded attempts. Every arm receives the supplied materials for its work order; independent acceptance checks remain separate from worker tests.
Local configurations and frontier references are distinguished in each lane. A frontier result is not a same-model comparison. All included outcomes remain visible; missing results are not zero-cost runs and do not count as passes. Elapsed times and completion status are reported separately.
These are selected development work orders. The original and follow-up recording windows, model settings, tool policies and time limits are documented with each card.
Reading an outcome
PASS: project accepted and clean harness completion. OUTPUT_ONLY: the artifact passed but the run did not reach accepted completion. FAIL: a required check failed. Timeouts and unrecorded tasks remain visible.
Passing independent groups alone does not override a failed public suite or protected-file check. Accepted project and clean finish are separate facts. The independent groups check the supplied work order.
Clocks & counters
Replay aligns each run's recorded start to zero. Runs did not all start simultaneously. Counters use actual saved response times, not animated estimates. Untimed evidence is not assigned an invented timestamp.
Input includes cached input; fresh input excludes cache hits. These three numbers are not additive. Partial metering displays only the measured subset, with coverage disclosed. Unknown never means zero. Native reports and server windows are overlapping scopes, not extra tokens.
The recorded work
The measurement download contains the task identity, outcomes, timings and token receipts used by this page. Reviewed work records provide the associated actions, checks and delivered files. Qualification history contains selected editions, not every development experiment; earlier included failures are retained.
The page runs without telemetry. Source hashes bind the displayed measurements to their saved records.
Source summary SHA-2563d2afef28724b6ea7896a7bd2ce5217505c3e4008afed8c95cf028a514ae05c5
Put your model to work.
Your model.
A better factory.
Recorded results, ready to explore.