Rule 1: Only one mouse is allowed to move at every single time.
Rule 2: What is a context window???
Rule 3: SD CARD CORRUPTION
Rule 3: SD CARD CORRUPTION
Rookie mistake. Next time store your swapfile on Google Drive so it's their problem!
You joke, but I did something like that. I NFS mounted a disk off my desktop to a RPi. I then made a swap file on the NFS file system.
I could then build a C++ project directly on the RPi because the build normally hit RAM limits. This was a 1st gen RPi, so it had 256MB RAM.
The build took forever (many days), but the program ran fine once built.
Tangential, but stuff like this makes me wish Intel's Optane had taken off. It was supposed to have the persistence of an SSD with performance near that of RAM, but it was expensive and the OEMs who included it relegated it to little more than a glorified drive cache.
Imagine being able to allocate some of your spare storage as extra RAM the same way the Pi lets you decide the RAM/VRAM split. Or more realistically, sticking your swapfile on it and your build not taking several days even though you're only working with a quarter gig of RAM.
I swear microSD is only marginally better than DVD-RW
I had to purchase a new dashcam recently, and I specifically picked up one that could save to a USB C SSD instead of its SD card because my previous VIOFO A129 would constantly corrupt its SD card.
Rule 3: SD CARD CORRUPTION
The Pi 4 and later can use a USB drive instead of a SD card for the OS drive. It's way faster and less prone to corruption.
I say this, despite noticing which sub we are in. ;p
Or an SSD, for storage too.
Rule 4: If it is mine either the soc cracks or the pmic.
Rule 2: What is a context window???
Its the window through which you enviously stare at people running megatoken context windows.
The problem is not enough RPis. If you get enough running in parallel, you achieve AGI, Nirvana, and quite possibly exit velocity.
oh no, OP will now buy all RPi stock and manufacturing capacity for years! what have you done?!
I mean, that's essentially how it works at every scale. When it says thinking, the first part of that wait is your query waiting in a queue
Use one of those CLI tools that show you the actual thinking process then. There's a LOT of LLM output between tool calls and code edits. Claude Code doesn't show it because a lot of it is dumb as a bag of rocks lmao
"expert"
I actually have a 3B running on my Home Assistant, an 8th gen NUC with 16G of RAM I got for $175. It's quite snappy... if not terribly correct about everything. It's capable of running an 8B but then the response time on the Voice PE is too slow to suit me (goes from 3 seconds to about 8 seconds).
What model are you running?
Qwen 2.5.
Can it be used for agentic workflows or just simple Q and A?
Yeah that's why I'm running it. Couldn't get reminders to work with all the possible permutations of time notation without an LLM. It still doesn't fully work properly but it's good enough and it has the side effect that it can answer any question you ask, for better or for worse. It gets simple things right more than half the time I'd say.
I'm keeping my fingers crossed that the work being done by groups like GLM will allow something smarter to run on this hardware within the next year or so.
what
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
