Kimi K3.1 scores 55 on Artificial Analysis, placed on the Pareto line
Posted by theanonymousone 1 day ago
Comments
Comment by lnenad 1 day ago
Comment by mppm 1 day ago
Comment by logicprog 1 day ago
Comment by jascha_eng 1 day ago
Although even this one needs to be taken with a grain of salt. Fable/Opus still act very differently to Astra and Argon imo. But maybe it's just because I am used to these. I wouldn't clearly put them above each other though, although I still prefer anthropics models, but that could be simply out of comfort.
Comment by switchbak 1 day ago
The only exception on the chart is DeepSeek - it scores exceptionally low there, which doesn't exactly track my experience. It usually does what you tell it to, and it's not exceptionally intelligent, but I do find it quite good at what it does (the bulk of code, scripting, etc). I know a lot of folks like it too ... curious if I'm just not exploring the simpler models enough?
Comment by lnenad 1 day ago
Comment by mijoharas 1 day ago
I keep having problems with them not doing the thing I ask, (and also failing to call tools correctly in pi. I think they've very much trained to the harness, which is frustrating.).
Comment by tonfreed 1 day ago
Comment by benregenspan 1 day ago
Comment by dom96 1 day ago
I think looking at some more niche benchmarks helps, I created one and it does show Kimi K3.1 Pro as the most intelligent of all open-weight models, though it is still significantly below Opus 5/5.5[1]
Comment by Bolwin 1 day ago
Comment by dom96 1 day ago
Comment by stymaar 1 day ago
Comment by lnenad 1 day ago
Comment by CharlieDigital 1 day ago
If you're in a stable codebase with lots of best practices, patterns, controls (linters, analyzers, etc.), examples already established, then any model will do ~the same plus/minus since there's not much novelty.
If you're building ground up, entirely novel, no reference, I think results will vary with lower capability models.
For me, I do a mix, leaving implementation to Haiku/Luna/DeepSeek and research/feedback/critique to Opus/Sol/Astra/Fable
Comment by ozgung 1 day ago
Comment by lnenad 1 day ago
Comment by mwigdahl 1 day ago
I would love a benchmark suite that better reflects real-world coding performance, as having Muse Wonder in the top three makes no sense to me.
Comment by weego 1 day ago
I took the output and original specs and handed them to Claude today and the level of insight and concise detail in it's criticism and problem solving was fantastic. Dropped the others immediately
Comment by lnenad 1 day ago
Comment by irthomasthomas 1 day ago
Comment by lnenad 1 day ago
Comment by CuriouslyC 1 day ago
Comment by rubinstein99 1 day ago
Comment by potsandpans 23 hours ago
The harness I've built for it is pretty straight forward: split binary into individual functions, give the agent a bunch of small tools to diff output with underlying binary, make them wrote clean c until there's a certified match.
Rin a final oracle to make sure the agent isn't cheating.
- Qwen 3.8 27b on my 5090, barely acceptable, thinks too long, sometimes freaks out.
- deepseek flash variants, work horse. Runinfra provides around 300 tok/s. Great for tearing through moderately complex functions
- glm and kimi k.3, expensive, slow, ultimately not that much better than deepseek flash for this task. Better at doing long context research into old compiler productions
- sol 6.1, best bang for buck. Creative enough to methodically work through more complex spellings
But I found there were around 1% of functions that these models simply cannot solve. Opus and Astra take them handily.
I'm still still in the process of looking through the solution traces, but from watching the missing sauce seems to be creative reasoning.
Sol 6.1 will just happily grind on permutations of a base shape spelling that M2C outputs, where opus and Astra immediately realize that they need to unwind assumptions taken for granted (and sometimes in the process endure a worst match).
I'm hoping to be able to capture that creativity step and distill it into the harness tools.
Comment by Incipient 1 day ago
I don't have much experience with anything outside of Claude for frontier models (and only haiku/3.x flash/5.6+6 luna at the entry level) so take this with that in mind.
I find Fable is still SIGNIFICANTLY 'smarter' then opus 5.5 when figuring out HOW to do something that's non-mechanical (e.g. How should we handle this aspect of business logic?"). Opus comes up with perfectly usable options, however Fable more often comes up with options that are more aligned with what I expect, or accept.
Comment by jawns 1 day ago
Comment by ghasemi 1 day ago
Comment by nektro 1 day ago
Comment by dgellow 1 day ago
Comment by probst 1 day ago
I really want to love this model, particularly since it's good to have an open weight model on my team so to speak, but I think I might be holding it wrong.
What are you using it for?
Comment by joshheitzman 1 day ago
I'm also using it with my own harness (you mentioned "in my harness"), so I'll share two things I found about using open weight model providers. The first is that getting the configuration right isn't a per model thing, its a per model per provider per point in time thing. The point in time thing comes from middleware updates as those introduce or fix defects that can very seriously impact inference quality. The second thing is inference quality varies a lot between providers, even when they are ostensibly using the same quant of the same model.
If you want to try it something else for comparison I open sourced my harness a couple of weeks ago: https://fluximp.org
I recommend trying deepseek v4.1 flash from together.ai (not the 1017 one the one released last month). deepinfra.com is cheaper for that but its noticeably slower and the inference from together.ai feels like it might be better (not quantified; just vibes).
Comment by samtp 1 day ago
On an overall speed/cost/quality comparison, it seems unmatched in my experience these days.
Comment by switchbak 1 day ago
Comment by amelius 1 day ago
Comment by esafak 1 day ago
Comment by andriy_koval 1 day ago
Comment by 0xc133 1 day ago
Comment by andriy_koval 1 day ago
Comment by stymaar 1 day ago
Comment by Onavo 1 day ago
For tasks like crawling and real time log analysis etc., the costs really add up at scale.