创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

用户称双256GB M5U聚类不如分别运行

AI 总结

Reddit用户称,将两台256GB M5U聚类后的效果不如分别运行两个模型,原因包括并发问题和解码速度提升不稳定。该用户目前在本地运行Qwen Flash Next q6和GLM3.5 Flash q4,并通过API使用DeepSeek;其个人体验显示,GLM q4的编程表现优于该API。

深度见解

这为评估大内存本地LLM硬件提供了社区实践参考,但帖子未提供受控基准测试,结论属于个人经验。

Just an update for anyone looking to get the m5u and thinking about clustering.

I tried clustering but I think running 2 separate models gets significantly better results. The current clustering technology (tensorfold/exos, etc) just isn’t there yet. Especially due to concurrency and the fact that decode doesn’t improve consistently as much as you would hope.

Currently I’m running Qwen flash next q6 and GLM3.5 flash q4. I also have Deepseek on API (from Deepseek). I was previously running 2x Qwen flash but decided to give GLM a shot. GLM is very smart. I’ve found that even q4 is better than my Deepseek API for coding. Qwen is great as the face because it is fast.

I actually think GLM5.3 is slept on. The reports it produces are 100x better than Qwen and Deepseek.

One problem is that 256gb isn’t enough for GLM if you want 500k+ context. I’m stuck at 260k for 3 agents max. And setting it up is finicky. I set my hot cache to 32gb and it caused me to run out of ram which makes speeds drop 70%. So there definitely is some value in the 512gb version of the m5u (hopefully newer version make the kv cache cheaper on RAM).

If anyone has any better optimizations or ways to run things on the 2 256gb m5u I’m all ears.

submitted by /u/Viktri1 [link] [comments]

#M5U#TensorFold#Exos#Qwen Flash Next#GLM3.5 Flash#DeepSeek

原文约 1 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。