Shimitar

Really

Never ever heard of

Thanks for quality post

(Luckly immich is much better quality than this post)

You actually WANT to be with low free memory. Provided that most of it is used by cache.

Free memory is a waste, when you could cache stuff for faster access.

That’s how Linux memory management works, and it make sense if you relflect on it. Better cache that page or that file that is used often, since free memory is just wasted. Cache can be freed and memory reclaimed in a fraction of a millisecond when needed.

So don’t bother too much. Unless your SWAP usage is high, don’t bother.

Also consider that Linux kernel will use your swap a bit even if you have lots of cache, because the kernel knows better than you how to improve your performances. Swapping out never used stuff is better than killing cached items.

Again, don’t oberthink memory on Linux, the best alarm is when swap is constantly happening, then yes you need more ram (or to kill that broken process that keeps hogging due to a bug)

My recent experience regarding questions on documentation:

• dovecot: shitty useless responses, totally made up
• Gentoo linux: to be checked twice and mostly wrong or fake
• godot: accurate and correct almost always, maybe examples not always 100% correct
• C++ standard 17: correct, never had a wrong reply from llm, also the exact ples where on point and correct

I think that’s all what I have used it for in the last six months.

Note: I used only Google search AI llm, nothing else.

So it seems that depends on what you ask.

Maybe you should check 5hat again. I never used llm before 2025, but proved itself useful for a few tasks. Yes check and verification still needed, but indeed made my life easier and got taken done faster. Quality was still a good as what I could do myself. Maybe that doesn’t speak well of myself I don’t know.

While you are correct, as all tools AI is not bad per se.

If you use ai to replace more lengthy documentation searches and write your own code that works out pretty well and speed up your work without degrading your coding. Granted, I got plainly incorrect answers as well, but at least I managed to be much more efficient.

Treat LLMs/ai as a glorified documentation aggregator and that’s how you correctly use that tool.

Like, use a knife to cut and cook meat, not to cut another person body, and that’s how you correctly use that tool too.