Remix.run Logo
▲ a11r 2 hours ago

Artificial analysis shows this: underperforming Qwen3.8 Flash Next and GLM 5.3 Flash, both of which you can run on a single B300 . I think Meta has a bit of catching up to do in the open-weight space.

As an aside, it's really unfortunate that artificial analysis only provides comparison at the highest reasoning level, which is mostly unusable for high-volume production use cases. I would really like them to start providing comparisons at low and medium reasoning levels across these models because those tend to be the ones that actually get used in production.

▲alexpotato 25 minutes ago | parent | next [-]

Been using GLM 5.3 Flash via Ollama Cloud basic subscription:

if this is the only model I had to use for the rest of my life, I would be cool with that. It's good at a wide variety of tasks including reverse engineering, design, working with ESP 32 etc.

I think Muse Spark 1.3 is better but GLM 5.3 Flash is an excellent daily driver.

▲samtp 23 minutes ago | parent | next [-]

I've been using GLM 5.3 Flash as the planner and DS 4.1 as the task worker over the last month and the results have been very good, predictable, ridiculously cheap.

▲neya 21 minutes ago | parent | prev [-]

If you liked GLM 5.3, you would appreciate Deepseek V4 Flash a lot. In my personal opinion and use-cases, it outperforms GLM 5.3.

▲0xbadcafebee 11 minutes ago | parent [-]

V4 isn't the newest DeepSeek, and GLM 5.3 non-Flash isn't the same ballpark

- DeepSeek V4.1 Flash has marginally better coding, and smaller experts (8B-In/16B-Out) with more compressed attention and KV cache, so it's faster but will have less expertise per task. It's a 552B model, so while it theoretically may contain more trained data it also requires more RAM (the experts are smaller to compensate for speed loss) making it harder to serve without the distributed KV cache DeepSeek hosts.

- GLM 5.3 Flash has marginally better agentic work, and has video input (DS doesn't), and its experts are 18B so there's more intelligence per task. It's a 320B model so it requires less RAM which will make it cheaper to serve. Considering it's a much smaller model, the higher intelligence indicates their architecture/training is better.

- GLM 5.3 (non-Flash) is far more intelligent than both; it's a 744B model with 40B experts, but it's text-only.

▲hadlock an hour ago | parent | prev | next [-]

I agree, however It's too easy to game arbitrary limits like "medium". There is no olympics for "just rolled out of bed and slightly hungover"

▲RussianCow an hour ago | parent | next [-]

You don't need to directly compare the same reasoning levels. Today you can compare Sol on Low vs Haiku on Max, for example, but you can't look at GLM 5.3 High, only Max.

▲leidenfrost an hour ago | parent | prev | next [-]

We don't even need a standard for reasoning levels.

Just accept whatever the provider names as "medium" and compare the accuracy between models vs the time it takes to complete a task.

▲jchw an hour ago | parent | prev | next [-]

For some tasks I genuinely feel Opus 5.5 does better on low than medium or high. The trouble, as always, is figuring out which.

Edit: I realize after commenting that you're not suggesting medium is useless, but just arbitrary and differs between models. Personally I don't want to directly compare mediums between models, I just want to be able to compare across effort levels.

▲disiplus an hour ago | parent [-]

i run opus on medium, sonet on high, and haiku on high for implementation based how complicated is for planing and specing and review opus is on high usually, except if if the task is contained.

did not try to run it on low, will have to try it.

▲eli an hour ago | parent | prev | next [-]

A graph of time (or cost) per task against success rate does it. Just include all the different levels.

▲Kinrany an hour ago | parent | next [-]

This exactly. The three interesting parameters are total time to answer, total cost, and output quality (for any given purpose).

▲arxo an hour ago | parent | prev [-]

[flagged]

▲esafak an hour ago | parent | prev [-]

That's the beauty of the line charts; the labels are arbitrary points on the line. You can easily compare the series visually.

▲oliwary 21 minutes ago | parent | prev | next [-]

The most important graph for me on Artificial Analysis is this: https://artificialanalysis.ai/?agentic-speed=intelligence-vs...

It shows the time to complete a task versus intelligence index, which is much more important for my use-case as I do quick back and forths usually. Someone on here suggested it to me a while ago. It also captures speed and token efficiency nicely, since both of these decrease time per task.

▲disiplus an hour ago | parent | prev | next [-]

this is properly bad as you can run glm on 6000pro, at (in my eyes) pretty good quant, and a q2 on a 5090. im suprised at how good 5.3 flash is at some parts. i still think ds4.1 flash is better but it is more demanding. i hope meta pushes something in a range of 300-400b with a 15-20b active parameters. i know its a crowded space. but it would be fast and probably mostly good enough.

▲AustinDev 40 minutes ago | parent | prev | next [-]

Yep, just benchmarked it against GLM5.3 Flash on my own local bench and it's slower in TTFT, tok/s and concurrency. It also scored lower.

Tried different reasoning levels and didn't really see any difference but GLM 5.3 flash only really works high, max or none so I couldn't really compare the lower efforts which appear to work on Spark.

▲drob518 24 minutes ago | parent | prev | next [-]

My immediate reaction is that it’s weaker on coding than other open-weight models and that coding is a primary use case for running locally (not the only one, but surely a major one). That said, it takes a lot to get full Kimi and GLM running locally.

▲RussianCow an hour ago | parent | prev | next [-]

> As an aside, it's really unfortunate that artificial analysis only provides comparison at the highest reasoning level, which is mostly unusable for high-volume production use cases. I would really like them to start providing comparisons at low and medium reasoning levels across these models because those tend to be the ones that actually get used in production.

The frustrating thing is they started doing this for the big labs—you can see their benchmarks for all reasoning levels of Sol 6.1 or Haiku 5.5. They just don't seem to do it for any of the open weight models.

▲Xenoamorphous an hour ago | parent | prev | next [-]

There’s a reason they put the “US” in “the most capable US open weight model”.

▲aniviacat an hour ago | parent | prev | next [-]

Artificial analysis puts it next to Mistral's new model.

▲halJordan 43 minutes ago | parent | prev | next [-]

Which is crazy bc they promised to open source muse 1.2 which is good. And they give us this bait and switch

▲lmeyerov 43 minutes ago | parent | prev | next [-]

yeah for botsbench.com side where we do cybersecurity investigation evals of models + harnesses, we've been having to play with:

1) time budget model gets (5min / task) -- this became a real problem with opus/astra/fable at high+

2) tuning which effort level we report on (when not all)

▲jmspring an hour ago | parent | prev | next [-]

Why didnt thry include OpenAI or Anthropic models? I get they were comparing open weights.

▲sebiandev an hour ago | parent | prev | next [-]

very true. when configuring custom agents for enterprise, we almost always default to none or low reasoning knobs. The added latency from medium or higher reasoning levels compared to the improvement in response quality is a diminished return.

▲segmondy 28 minutes ago | parent | prev | next [-]

AA is a joke.

▲dsco 38 minutes ago | parent | prev | next [-]

[flagged]

▲thefourthchime 38 minutes ago | parent | prev | next [-]

[dead]

▲ an hour ago | parent | prev | next [-]
[deleted]
▲ProblemExplorer 2 hours ago | parent | prev [-]

[dead]