Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
1–10 of 40 posts
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#2Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#3Flash 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.
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#4Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#5Flash 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.
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#6Flash 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.
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#7Flash 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'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.
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#8Flash 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.
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…
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#9Earlier 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
Re: Workhorse LLMs: Why Open Source Models Dominate Closed Source for Batch Tasks
#10Flash 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.
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 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 the resulting 1-shot output is on my github.I know it was in the training set, etc, but I wanted to see how big of a hassle it was, if it would 1-shot with such a small prompt, how long it would take.
Makes me want to try deepseek 671B, but I don't have any machines with >1TB of memory.
I do take donations of hardware.