Earlier quoted context omitted.
I have a small laptop. If you have more disks available, you could really do some testing. When you have some benchmarks, submit a pull request or issue so we can maybe work on them. We are really happy for contribute!
I have epyc 9654 ES and a 7900 XTX. I was running the numbers, and even if I maxxed out the ram to like 12x32 gig sticks, it would cost me thousands more and I could only run GLM-5.2 at a couple tokens per second at q3. So this project is very promising because it suggests I could get pretty high speed and this CPU/motherboard combination suggests I have a lot of pci bandwidth that is unused. I think another route mi…
Show HN: Getting GLM 5.2 running on my slow computer
221–230 of 269 posts
Re: Show HN: Getting GLM 5.2 running on my slow computer
#222After spending way too much time with Fable a few days ago, I noticed a new hallmark of AI generated text is using the word "honest" everywhere, in a somewhat self congratulating way. Some things that give it away to me: - "Honest numbers (WSL2, 12 cores, 25 GB RAM, NVMe via VHDX)" - "an honest peak projection (working set, KV, MTP row, reconstruction buffers) so the kernel OOM-killer never fires." - "Honest caveat f…
Re: Show HN: Getting GLM 5.2 running on my slow computer
#223I was actually just working on the same thing as this, but I went down the route of mmapping the entire model into memory to avoid the extra ram usage. I also had Claude implement Medusa[1] on the model to try and avoid loading an additional model into memory but still get the benefits of MTP. Currently at a stop light so I can't list everything and I didn't get to read your full post either yet. To expand since I ju…
Posting on the Hacker News forum is not worth risking your, or anybody else's, life.
Re: Show HN: Getting GLM 5.2 running on my slow computer
#224Earlier quoted context omitted.
I've been seeing a lot of usage of the word `real` from recent fable sessions: - That gap is the real story: 3,873 flows - the real conversion filter types are: - I'll update the breakdown query to include a column for each real type
I have almost completely stopped writing real in my own output as a direct consequence of this. Maybe next year they'll catch up with my alternative wordings and I'll end up switching back
Re: Show HN: Getting GLM 5.2 running on my slow computer
#225My main question is whether when put into practical use, this can be measured in tokens/second, or more like 1 token per minute... I have seen locally hosted LLM that are as slow as 1 tok/second still be very useful if you give it a project to do something overnight and metaphorically walk away from it, check back with what it has done in 6 or 8 hours. 0.05 to 0.1 tok/s on the other hand, as reported in the URL for t…
Now many mini-PCs and desktops are able to read simultaneously from 1 PCIe 5.0 SSD and 1 PCIe 4.0 SSD. This can ensure a reading throughput around 20 GB/s, i.e. 20 times faster than on author's system. With only 1 PCIe 5.0 SSD, the reading throughput is still significantly more than 10 times faster than on author's system. So it is likely that inference speeds around 1 token/s are achievable on something like a NUC m…
The benchmarks I'm seeing for many of them don't really make me think that a pair of consumer grade NVME SSD you could fit in a mini-PC or mini-itx size desktop would, added together, be capable of 20GB/s reads.
Re: Show HN: Getting GLM 5.2 running on my slow computer
#226What I'd like to see personally is Small Language Models giving similar performance eventually (because do we really need that many hundred billion parameters?). Researchers have shown that a lot of attention heads in the LLMs we're using these days are barely even active, so the MoE architecture seems like a step in the right direction. I still wonder how far we can push things back towards a 1B or 3B parameters model while trying to reach similar performances as double-digit or triple-digit B params models.
Re: Show HN: Getting GLM 5.2 running on my slow computer
#227I was actually just working on the same thing as this, but I went down the route of mmapping the entire model into memory to avoid the extra ram usage. I also had Claude implement Medusa[1] on the model to try and avoid loading an additional model into memory but still get the benefits of MTP. Currently at a stop light so I can't list everything and I didn't get to read your full post either yet. To expand since I ju…
> Currently at a stop light so I can't list everything and I didn't get to read your full post either yet. Posting on the Hacker News forum is not worth risking your, or anybody else's, life.
Re: Show HN: Getting GLM 5.2 running on my slow computer
#228I wonder if you could replicate this in a Colourful GeForce RTX 50-series GPU, they ship it with 2 NVMe drive slots.
Re: Show HN: Getting GLM 5.2 running on my slow computer
#229After spending way too much time with Fable a few days ago, I noticed a new hallmark of AI generated text is using the word "honest" everywhere, in a somewhat self congratulating way. Some things that give it away to me: - "Honest numbers (WSL2, 12 cores, 25 GB RAM, NVMe via VHDX)" - "an honest peak projection (working set, KV, MTP row, reconstruction buffers) so the kernel OOM-killer never fires." - "Honest caveat f…
I've been seeing a lot of usage of the word `real` from recent fable sessions: - That gap is the real story: 3,873 flows - the real conversion filter types are: - I'll update the breakdown query to include a column for each real type
Re: Show HN: Getting GLM 5.2 running on my slow computer
#230Earlier quoted context omitted.
I've been seeing a lot of usage of the word `real` from recent fable sessions: - That gap is the real story: 3,873 flows - the real conversion filter types are: - I'll update the breakdown query to include a column for each real type
I have almost completely stopped writing real in my own output as a direct consequence of this. Maybe next year they'll catch up with my alternative wordings and I'll end up switching back
“Something something main point — but also pay attention to this related thing — finish main point.”
Anecdotally, it seems to produce more consistent results when I “speak its language”.
On the output side, I’ve become much more aggressive about trimming and editing any prose it produces that I intend on sharing. Both for my own benefit to improve comprehension, but also because dumping the raw, verbose output on my colleagues feels lazy and disrespectful of their time.