Backend comparison

Qwen 3.8 vs Kimi K3

Compare Qwen 3.8 and Kimi K3 using each model’s highest published backend score, with its recorded effort and evaluation date.

Backend & testing

Kimi K3 / high leads these published backend results by 6 points. Kimi K3 / high completed 9m 52s sooner. Reference costs are available for both configurations.

Published backend evidence
Published
Oct 27, 2026, 12:22 AM UTC
Question pack
coding-fast-v4.12
Tested
2 measured configurations
Batch
pricing-558102e552269389e09ab11477f8c63d3aedee5bab43565c55e4168c61b36cf4

This is a publication snapshot of retained results. Evaluations may have completed on different dates; these scores describe the backend axis, not the three-axis overall score.

Published backend results

MeasureQwen 3.8 / defaultKimi K3 / high
Backend configuration rank#64#46
Backend score64/10070/100
Backend testedSep 9, 2026, 09:53 PM UTCSep 9, 2026, 10:01 PM UTC
Elapsed47m 48s37m 56s
Reference cost$1.07$0.89
RouteCustom endpointCustom endpoint
Black-box Regression Audit12/2016/20
Retry Planner Counterexamples17/2015/20
CI Adversarial Audit8/2014/20
Transaction Regression Design14/2012/20
Cache Propagation Certificate13/2013/20

How to choose from these results

Does the measured quality difference remain useful after you account for route reliability, elapsed time, and your own task profile?

Start with the backend score and question profile. Use elapsed time only after both configurations clear your quality floor, and leave cost undecided when either side is not covered.