Live data from Hacker News

Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

sutro.sh

11–20 of 40 posts

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#11
post #3

Earlier quoted context omitted.

You're getting downvoted but what you said is true. The cost of self-hosting (and achieving +70 tok/sec consistently across the entire context window) has never been low enough to justify open source as a viable competitor to proprietary models of OpenAI, Google, and Anthropic.

I am curious the need for 70 t/sec?

Waiting minutes for your call to succeed is too frustrating?

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#12
post #9
post #8

Earlier quoted context omitted.

It does not take dozens of hours to get an API key for gemini

I never claimed that it did. Gemini would probably save me the same dozens of hours, but come with ongoing costs and additional starting up hurdles (some near insurmountable in my organisation, like data security for some of what I'm doing).

Gemini flash or any free LLM on openrouter would be orders of magnitude faster and effectively free. Unless you are concerned about privacy of the conversation - it's really purely being able to say you did it locally.

I definitely do appreciate and believe in the value of open source / open weight LLMs - but inference is so cheap right now for non frontier models.

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#13
post #2

Flash is just so obscenely cheap at this point it's hard to justify the headache of self hosting though. Really only applies to sensitive data IMO.

You'd be surprised how often people in enterprise can be left waiting months to get an API key approved for an LLM provider.

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#14
post #8
post #6

Earlier quoted context omitted.

With tools like Ollama, self-hosting is easier than hosted. No sign-up, no API keys, no permission to spend money, no worries about data security, just an easy install then import a Python library. Qwen2.5-VL 7B is proving useful even on a work laptop with insufficient VRAM - I just leave it running over a night or weekend and it's saving me dozens of hours of work (that I then get to spend on other higher-value work…

It does not take dozens of hours to get an API key for gemini

They weren’t saying getting the api key would take that long, just getting permission from their company to let them do it.

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#15
post #2

Flash is just so obscenely cheap at this point it's hard to justify the headache of self hosting though. Really only applies to sensitive data IMO.

There is a wide range of opinions on what should be considered sensitive data. Many people would classify a vast majority of their data as sensitive.

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#16
post #11

Earlier quoted context omitted.

I am curious the need for 70 t/sec?

Waiting minutes for your call to succeed is too frustrating?

Depends entirely on the use case. Not every LLM workflow is a chatbot

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#18
post #13
post #2

Flash is just so obscenely cheap at this point it's hard to justify the headache of self hosting though. Really only applies to sensitive data IMO.

You'd be surprised how often people in enterprise can be left waiting months to get an API key approved for an LLM provider.

Are you saying that it's faster for them to get the hardware to run the weights themselves? Otherwise I'm not sure what the relevancy is.

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#19
post #6

Earlier quoted context omitted.

With tools like Ollama, self-hosting is easier than hosted. No sign-up, no API keys, no permission to spend money, no worries about data security, just an easy install then import a Python library. Qwen2.5-VL 7B is proving useful even on a work laptop with insufficient VRAM - I just leave it running over a night or weekend and it's saving me dozens of hours of work (that I then get to spend on other higher-value work…

I got the 70b qwen llama distill, I have 24GB of vram. I opened aider and gave a small prompt, roughly: Implement a JavaScript 2048 game that exists as flat file(s) and does not require a server, just the game HTML, CSS, and js. Make it compatible with firefox, at least. That's it. Several hours later, it finished. The game ran. It was worth it because this was in the winter and it heated my house a bit, yay. I think…

Buy a used workstation with 512GB of DDR4 RAM. It will probably cost like $1-1.5k, and be able to run a Q4 version of the full deepseek 671B models. I have a similar setup with dual-socket 18 core Xeons (and 768GB of RAM, so it cost about $2k), and can get about 1.5 tokens/sec on those models. Being able to see the full thinking trace on the R1 models is awesome compared to the OpenAI models.

Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks

#20
This is a useful analysis, but only as a first cut and sometimes not even that -- Grok 3 mini and DeepSeek V3 are by far the least expensive coding models that are worth trying for scenarios where you do and don't care about the vendor training on your requests, respectively. One of those is "open source" (by which he seems to mean "open weights") but far too large to run locally.

[I guess that must be a useful market niche though, apparently this is by a company selling batch compute on exactly those small open weights models.]

The problem is the author is evaluating by dividing the Artificial Analysis score by a blended cost per token, but most tasks have an intelligence "floor" below which it doesn't matter how cheap something is, it will never succeed. And when you strip out the very high results from super cheap 4B OSS models the rest are significantly outclassed by Flash 2.0 (not on his chart but still worth considering) and 2.5, not to mention other models that might be better in domain specific tasks like grok-3 mini for code.

(Nobody should be using Haiku in 2025. The OpenAI mini models are not as bad as Haiku in p/p and maybe there is a use case for prefering one over Flash but if so I don't know what it is.)

Post reply on HN