Command A vs Yi-Large benchmark

Interactive Comparison Diagram

Recommended Workload Routing

Frequently Asked Questions

Which is better overall, Command A or Yi-Large?

Yi-Large has the higher preference Elo in our latest snapshot (1,430). “Better” still depends on coding, price, and latency — see the table.

Which is better at coding, Command A or Yi-Large?

Yi-Large leads SWE-bench at 53.8% vs 42.6%. SWE-bench is one harness, not your repo.

Which is cheaper to run in production?

Yi-Large output tokens are $0.3/1M versus $10/1M. Input prices and retry rates still move the real bill.

Which is faster, Command A or Yi-Large?

Command A has the lower time-to-first-token (175 ms vs 220 ms). Tokens/sec is a separate column if you care about long completions.

Which has the larger context window?

Command A accepts 256k tokens versus 33k.

Can I self-host either model?

Neither model is marked open-weights here. You are comparing hosted APIs.

Are these scores from CompareLLM’s own evals?

No. V1 aggregates public leaderboards (and optional first-party latency pings). Each cell names its source and date. Read /methodology.

What does preference Elo mean on this page?

Preference Elo is a crowd vote from LMArena / Arena. People see two hidden answers and pick the one they like more. The model that wins more often gets a higher Elo. That means people preferred it — not that it passed a school test. It is not SWE-bench, not accuracy, and not a number we invent. Command A and Yi-Large Elo cells are dated snapshots from the named source — we do not compute Arena ourselves.