DOPEST 1.0 31Bv1.7 · 10 s rule

Composite (secondary)

67.8 · Composite rank #25

Cost and measurement conditions

$0.049 per 1,000 decisions (estimated)

ESTIMATE (*est.), base-model market reference through the frozen pricing_v15 module (sha256 aa2afcd5a58d0c4cc0e3d6867d590c70b6ac58e971410c27faf9628f97bcf8b7, snapshot of 22 Oct 2026): base string google/gemma-4-31B-it (the adapter config's base_model_name_or_path, in the author's capitalised spelling) priced as google/gemma-4-31b-it USD 0.09/M input and USD 0.34/M output; the output term is zero because output usage is zero. The exact case of 31B is required by the frozen module: it resolves to the lowercase google/gemma-4-31b-it listing, while the all-lowercase spelling raises 'base model lacks an explicit market-listing decision' here. No explicit reference or override is used. Estimated, not charged, not a quote from the author or any host. Tokens as reported natively by the usage block of the author's server: 990,293 input and 0 output tokens across all 1,500 answered items; no generated text. Native usage equals our first-party offline count exactly (0 mismatches over 1,500 items; our sealed-input count was also 990,293 and the prompt-level concordance had 0 mismatches). The 15 items that the author's 12,288-token prompt limit truncated are answered and are INCLUDED in the usage and in the cost (their counted input is the truncated prompt, at most 11,985 tokens). Under the zero-output convention for native-probability rows (the published native-probability convention, as applied to Vera and Turion) the output term contributes nothing. Measured arithmetic: USD 0.059417580 per 1,000 decisions over all 1,500 rows = 0.919852886x the unchanged USD 0.06459465517241379 cap; separately USD 0.049372545 per 1,000 on the common 1,485-item basis (814,647 input tokens; the same items for every token-priced row, which excludes the draw's 15 standard long positions) = 0.764344129x. WITHIN COST CAP on both bases: within the automatic cost treatment; no cap exception or top-up. The all-1,500 figure is close to the cap (0.92x) while the common-basis figure is 0.76x, so the measured number, not the pre-run forecast, decides.

x2 + 0.15 s (assumption, not measured)

Evaluator-owned rented Verda GPU VM, one NVIDIA A100-SXM4-80GB (81,920 MiB, driver 580.178.04), FIN-03 (Finland, EU), PAYG non-spot, USD 2.2311917808219177/h recorded by the runner, 300 GB OS volume. One VM for this row's measured attempt. Measured 25 Oct 2026, VM window about 17:22-18:03Z, about USD 1.53 GPU rental (elapsed time at the recorded hourly rate; attempts 1 and 2 are not included in that figure). Author server at 127.0.0.1:8000 in a --network none --read-only, cap-drop-ALL container started through env -i: read-only code, model and input mounts, tmpfs caches, private output, empty provider credentials (DEEPSEEK, OPENAI, HF, MODAL, OP) and HF offline flags. Before sealed input: in-container network cut proven (only loopback, no IPv4/IPv6 default route, DNS and TCP fail); model files re-hashed (12 files, 0 failures); a synthetic pre-warm passed on the first try; the TTL fit gate admitted the run. Input sha256 dfd36720077ef7c41ace367524896507c7f44ce71306fb3e659e8b85069d995b was re-checked inside the container (match). Complete 1,500-row run, rc 0; scored loop 516.0 s. Raw output sha256 33fe1dc0d85a195fe0bd65d1d0a0fb21c9d78abc1d6c72631eceec306bf33ee8 (the pull-hash receipt). Node-shred and local-shred receipts verified; exact-id teardown receipt confirms the VM closed. GPU rental is separate from the benchmark's estimated model tariff.