helexa/helexa
1
0
Fork 0
Code Issues 105 Pull Requests Actions Packages Projects Releases Wiki Activity

bench: reproducible benchmark harness + published numbers #22

New Issue
Open
opened 2026-06-12 08:47:23 +00:00 by grenade · 2 comments
grenade commented 2026-06-12 08:47:23 +00:00
Owner
Copy Link

There are zero benchmarks in the tree. The 7/10 rating rests on unproven performance; this issue either proves it or tells us exactly what to fix.

Why: the single biggest credibility artifact. "Near-frontier AI for mortals" needs a table an outsider can verify.

Deliverables:

  • a committed harness (script or crate) that runs the same model + quant on helexa vs llama.cpp/Ollama (and vLLM where it fits consumer VRAM)
  • measures what one operator feels: TTFT at realistic agent prompt lengths (4k–32k), batch-1 decode tok/s, cold-load time
  • run on the real fleet (3060 / 4090 / 5090), including the heterogeneous-TP configuration peers cannot run
  • results published as doc/benchmarks.md; headline numbers surfaced in README

Dependencies: #21 (token-level metrics) for engine-truth measurement.

There are zero benchmarks in the tree. The 7/10 rating rests on unproven performance; this issue either proves it or tells us exactly what to fix. **Why:** the single biggest credibility artifact. "Near-frontier AI for mortals" needs a table an outsider can verify. **Deliverables:** - a committed harness (script or crate) that runs the same model + quant on helexa vs llama.cpp/Ollama (and vLLM where it fits consumer VRAM) - measures what one operator feels: TTFT at realistic agent prompt lengths (4k–32k), batch-1 decode tok/s, cold-load time - run on the real fleet (3060 / 4090 / 5090), including the heterogeneous-TP configuration peers cannot run - results published as `doc/benchmarks.md`; headline numbers surfaced in README **Dependencies:** #21 (token-level metrics) for engine-truth measurement.
grenade added this to the 7 → 8 milestone 2026-06-12 08:47:23 +00:00
grenade added the p1-now label 2026-06-12 09:01:45 +00:00
grenade commented 2026-06-12 12:39:54 +00:00
Author
Owner
Copy Link

PR #32 lands the harness (script/bench.py) and the first published numbers (doc/benchmarks.md, 2026-06-12): 1.7B@3060 81 tok/s, 8B@4090 62 tok/s, 27B@2×5090 Q6K TP=2 at a steady 35 tok/s with flat decode 128→4k — and the 4k-prefill TTFT of 7.1 s recorded as #23's before-number.

Remaining for full closure: the llama.cpp / Ollama comparison columns (same checkpoints, same hosts — the harness accepts any OpenAI-compatible base URL via --label, so adding them is an install-and-run exercise), and cold-load timing (visible per-deploy in the journal + deploy validation; tracked under #1).

PR #32 lands the harness (`script/bench.py`) and the first published numbers (`doc/benchmarks.md`, 2026-06-12): 1.7B@3060 81 tok/s, 8B@4090 62 tok/s, 27B@2×5090 Q6K TP=2 at a steady 35 tok/s with flat decode 128→4k — and the 4k-prefill TTFT of 7.1 s recorded as #23's before-number. Remaining for full closure: the llama.cpp / Ollama comparison columns (same checkpoints, same hosts — the harness accepts any OpenAI-compatible base URL via `--label`, so adding them is an install-and-run exercise), and cold-load timing (visible per-deploy in the journal + deploy validation; tracked under #1).
grenade added p3-later and removed p1-now labels 2026-06-17 13:34:00 +00:00
grenade commented 2026-06-17 13:34:12 +00:00
Author
Owner
Copy Link

Demoted p1-now → p3-later.

The unblocking core of this issue has shipped: the reproducible harness (script/bench.py) plus the continuous, version-aware helexa-bench (CLAUDE.md 2026-06-13 addendum), and the first published baselines (doc/benchmarks.md, PR #32 — 1.7B@3060 81 tok/s, 8B@4090 62 tok/s, 27B@2×5090 Q6K TP=2 ~35 tok/s). Token-truth measurement (#21) is done.

What remains is demand-driven, not active pain: the llama.cpp/Ollama comparison columns (install-and-run against the same hosts) and surfacing headline numbers in the release writeup. That output feeds #26 (tagged release + public writeup), which is already p3-later — so this sits alongside it, picked before #26 since #26 consumes its numbers.

Demoted `p1-now` → `p3-later`. The unblocking core of this issue has shipped: the reproducible harness (`script/bench.py`) plus the continuous, version-aware `helexa-bench` (CLAUDE.md 2026-06-13 addendum), and the first published baselines (`doc/benchmarks.md`, PR #32 — 1.7B@3060 81 tok/s, 8B@4090 62 tok/s, 27B@2×5090 Q6K TP=2 ~35 tok/s). Token-truth measurement (#21) is done. What remains is **demand-driven**, not active pain: the llama.cpp/Ollama comparison columns (install-and-run against the same hosts) and surfacing headline numbers in the release writeup. That output feeds #26 (tagged release + public writeup), which is already `p3-later` — so this sits alongside it, picked before #26 since #26 consumes its numbers.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
out-of-scope
Outside helexa's constraining principles: near-frontier models on consumer hardware, served transparently and predictably
 p1-now
Active pain or unblocking work — pick up first
 p2-next
Engine levers — start once P1 baselines exist
 p3-later
Dependent on earlier work, or demand-driven
No Label p3-later
Milestone
No items
No Milestone 7 → 8
Projects
Clear projects
No project
Assignees
Clear assignees
grenade
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: helexa/helexa#22
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?