logoalt Hacker News

LFM2.5-24B-A2B: Built for fast on-device agents

131 points • by gmays • yesterday at 11:59 PM • 35 comments • view on HN

Comments

ghotli • today at 5:06 AM

Maybe someone knows what order of cost a release like this requires in real terms of hardware and energy spend?

The cost over the diff from the moment of beginning training to the end. It's iterative from a prior model so it starts there and becomes this release after spending occurs I presume.

For example, is liquid spending millions in energy in this case and the cost is amortized over successive training runs over the initial datacenter spend? What if it's just eating cloud costs and has no dedicated hardware, that sort of thing. I don't particularly mean this model and liquid specifically. Just for this class of smaller fast on-device range of model what is the order of the training cost in real terms?

Maybe its short sighted to ask it as if it's a singular training run and is perhaps the end state of many variations of testing thus all of the R&D training runs would have to be included to to inform what became the final release. Seems like this should be taken into consideration. If anyone happens to know it'd be appreciated!

sebmellen • today at 12:18 AM

> it runs up to 1.7× faster than comparable MoEs on-device, with 184 tokens/s on an Apple M5 Max and up to 21K output tokens/s on a single NVIDIA B300 GPU

Wow, those are seriously impressive numbers for how intelligent this model seems to be!

One thing that this article doesn't clarify, and that I guess I really should look into, is what exactly AutomationBench tests for as compared to other benchmarks. The standout performance on AutomationBench is interesting to see, but I don't know what it really means because the model seems to score relatively close to other local models on every other benchmark.

➕ show 1 reply
2001zhaozhao • today at 1:02 AM

This seems like a big deal, no?

If Qwen had released a Qwen3.8 MoE of similar size, with a naive extrapolation its capabilities would roughly be similar to this model. So basically someone has caught up to Qwen (albeit Qwen from 1-2 months ago) in parameter efficiency.

➕ show 1 reply
stephantul • today at 5:09 AM

Does anyone know the order of magnitude licensing cost for the model for businesses over 10m in revenue?

MatthiasPortzel • today at 3:37 AM

[delayed]

ricardobeat • today at 3:35 AM

In a private benchmark I have, it performs much, much worse than Qwen 35B A3B for general knowledge. Still, probably beats Qwen 9B at much higher speed.

serf • today at 12:47 AM

i'm gettin between 200-320 tok/s on a 5070ti with 131k context on llamacpp and no tuning.

very nice.

I can't speak to the intelligence of it yet.

these small agentic-focused models are a lot of fun to play with if you haven't yet.

➕ show 1 reply
blinkingled • today at 2:38 AM

I asked it to implement the simplest todo in ghostty codebase and it failed badly - kept going in circles fixing one compile error and introducing another. Qwen 3.8 was slower (40 tok/s compared to 75) but did get it done.

➕ show 3 replies
nico • today at 12:48 AM

Love seeing the effort Liquid is putting into local models. I’m looking forward to a lot of progress here in the next 5 years

nico • today at 12:47 AM

> with 184 tokens/s on an Apple M5 Max

That seems pretty decent. How many tokens/s do you need for a coding agent to feel like Claude or codex?

➕ show 6 replies
fithisux • today at 4:34 AM

It is a good model for on-device work.

stogot • today at 3:51 AM

The license is generrous (free under <$10m) Pricing confusing when it shows API pricing 1st

CurbStomper4 • today at 2:07 AM

[dead]

machenh001 • today at 3:20 AM

[flagged]

snootypoot • today at 12:44 AM

[dead]