BTW a lot of it seems to be just inefficient coding as Deepseek has shown.
Kind of? Inefficient coding is definitely a part of it. But a large part is also just the iterative nature of how these algorithms operate. We might be able to improve that via code optimization a little bit. But without radically changing how these engines operates it won’t make a big difference.
The scope of the data being used and trained on is probably a bigger issue. Which is why there’s been a push by some to move from LLMs to SLMs. We don’t need the model to be cluttered with information on geology, ancient history, cooking, software development, sports trivia, etc if it’s only going to be used for looking up stuff on music and musicians.
But either way, there’s a big ‘diminishing returns’ factor to this right now that isn’t being appreciated. Typical human nature: give me that tiny boost in performance regardless of the cost, because I don’t have to deal with. It’s the same short-sighted shit that got us into this looming environmental crisis.
kescusay@lemmy.world 2 days ago
Coordinated SLM governors that can redirect queries to the appropriate SLM seems like a good solution.
sleep_deprived@lemmy.dbzer0.com 1 day ago
That basically just sounds like Mixture of Experts
kautau@lemmy.world 1 day ago
Basically, but with MCP and SLMs interacting rather than a singular model, with the coordinator model only doing to work to figure out who to field the question to, and then continuously provide context to other SLMs in the case of more complex queries
JoeKrogan@lemmy.world 2 days ago
Powered by GNU Hurd