Repository navigation
π³οΈ Vote: shape V2 β what should benchtest benchmark next? #1
Replies: 12 comments
|
FRAMEWORK β llama.cpp (llama-server) β π here to vote |
|
FRAMEWORK β Ollama β π here to vote |
|
FRAMEWORK β LM Studio (local server mode) β π here to vote |
|
FRAMEWORK β vLLM Qwen MTP builds (blocked upstream; vote to show demand) β π here to vote |
|
MODEL β Qwen3.8 smaller quants (8β16 GB RAM class) β π here to vote |
|
MODEL β Llama 4.x local quants β π here to vote |
|
MODEL β Gemma family (beyond the vLLM reference build) β π here to vote |
|
MODEL β MoE small-active models for 32β64 GB Macs β π here to vote |
|
HARNESS β Claude Code (local-endpoint mode) β π here to vote |
|
HARNESS β Codex CLI β π here to vote |
|
HARNESS β Cline / Continue (headless modes) β π here to vote |
|
HARNESS β Gemini CLI (OpenAI-compat endpoint) β π here to vote |
Uh oh!
There was an error while loading. Please reload this page.
π³οΈ Vote: shape V2 β what should benchtest benchmark next?
V2's framework list is a starting ballot, not the limit. How to vote:
every candidate below is posted as a separate comment β add a π
reaction to each one you want. Reaction count = votes. Write-ins: add a
new comment in the matching category and it becomes votable too.
Tallies are reviewed for each V2 milestone; top picks move onto the
roadmap in order.
Category 1 β Serving frameworks
(Each option below should be posted as its own comment by the maintainer;
voters react π.)
On the ballot to start:
Likely write-ins: MLC-LLM Β· TensorRT-LLM metal builds Β· other MLX
runtimes Β· anything with an OpenAI-compatible /v1 endpoint and a
CLI-launchable server.
Category 2 β Model families / quants for frozen campaigns
Vote for families worth a full published campaign. Include the RAM class
you'd run them on (16 / 32 / 64 / 128 GB) in a reply if you can β
smaller-RAM configs are first-class.
On the ballot to start:
Category 3 β Agent harnesses
On the ballot to start:
Rules of thumb: eligible = OpenAI-compatible
/v1endpoint +CLI-launchable server, reproducible by a community member on their own
machine. Be civil; one account, one reaction per comment (GitHub enforces
this naturally).
All reactions