@kalomaze the small gap between DSV4 flash and pro really makes you wonder what went wrong with the DSV4 pro training... is it just undercooked or is the arch inherently doesn't scale well...
@llmdevguy kimi k2.7 should be compared to composer 2.5 since they share a base model and differ in post-training... I'm skeptical that 2.7 can leapfrog composer 2.5...
@SzymonOzog_ haha :)) I have to admit my kernels were optimized on sm120 and were performing at 25% SOL on sm90, but opus 4.7 was only able to push it to around 40% before... Mythos reached around 70%
@dogacel0 It's clear that Mythos was RLd extensively on kernel generation using various new DSLs even... I made it go over my triton kernel and suggested rewriting them in CuteDSL which was super interesting as other LLMs usually don't even know about CuteDSL. then it made them 3x faster
@juliarturc@atmoio I think the same goal of "finding meaning" can be achieved by going down at least one level of abstraction, without the need to change careers.
@cognition Good stuff! hopefully the team will be fast in covering other models... would be nice to see DSV4, GLM5.1, Qwen3.7 Max, Composer 2.5, Gemini Flash 3.5, M3 etc. and also the SOTA local models like Gemma 4 31B and Qwen 3.6 27B
@thegenioo@datacurve The only model that sort of approaches 5.5 or 4.8 for my tasks (mostly ML and perf engineering) has been Qwen 3.7 Max, but it's still too expensive and slow. 5.5 remains undefeated, can't wait for 5.6
@htihle Any plans to test qwen 3.7 max? Itβs been by far the best chinese model for ML tasks in my experience. Although itβs very expensive per task even compared to 5.5 or 4.8