Thanks. I could neither find a file /var/log/kern.log nor did find /var/log | grep -i mess have a match.
Thanks. I could neither find a file /var/log/kern.log nor did find /var/log | grep -i mess have a match.
dmesg and journalctl -k, found only entries after reboot, that the shutdown was not clean. Any specific logs where I could find more?
Does on mean that /sys/kernel/mm/lr_gen/enabled returns 0x7?
Just set vm.page-cluster to 0, to disable the page read-ahead (AFAIK the default value was set when swap was still on rotating disks).
Debian does not enable it by default, cat /sys/kernel/mm/lru_gen/enabled will be a 0.
I am running Debian 12 on all of my devices with Debians vanilla kernel! :-) Just enable MGLRU on Debian like it is described in this blogpost.
One further tip for ZRAM: On my device the LZ4 algorithm was noticeable faster than ZSTD (didn’t try ZSTD with the enabled MGLRU, yet) and it was important to disable the RAM page read-ahead on my device.
deleted by creator
I don’t know either, but unless one uses zstd (lzo seems more like a thing for this hardware), I would hope that it is totally usable. (Running zstd memory compression on a Raspberry Pi 2, w/o any noticeable speed impact)
Show me some numbers! ;-) … Perhaps I miss something, but basically we have 32bit pointers vs. 64bit pointers, the rest of the data should be the same size. 64bit should be faster for tasks where the CPU is the bottleneck/computations, so IMHO it will be an interesting tradeoff with no clear winner for me.
The most important thing is not the distribution, but to enable ZRAM (or ZSWAP) and use a lightweight desktop. I am not sure how much difference a 32bit vs a 64bit distribution makes, but if possible you could take one for the team and run some trials and report your numbers (RAM usage) back here.
Of course I recommend Debian with a lightweight desktop of your choice, or Alpine.
Yes, Apple! :-) Obviously Apple doesn’t have the win margins to put proper parts in their hardware…
Just yesterday I realized my Thinkpad Edge 330 is running w/o any trouble for 11 years now, cost me little above 300€, brand new back then. :-)
Thanks, this would indeed solve my problem. Still hoping for a better solution, but if everything else fails I’ll utilize it!
Thanks, that would be a valid approach and my last resort.
As you said, I hope someone knows a more elegant solution, though!
Very happy to read that, but honestly, when reading “$1 million USD” as investment sum, it reads more like an advertisement stunt than a real investment. (Like, 2 senior developers for one year?)
We need more diversity in Open Source operating systems for desktops, laptops and any of the *BSDs is a great candidate. (Would love to see Haiku getting some sponsorship or even ReactOS!)
Ah, the usual propaganda from the fucking content mafia and the lobbyists they bought:
“The takedown of Fmovies is a testament to the power of collaboration in protecting the intellectual property rights of creators around the world,” Knapp says.
“Strengthening intellectual property rights is an important element of the U.S.-Vietnam Comprehensive Partnership,” Knapper said
I’ll happily repeat again and again and again:
Seriously, fuck all the politicians and governments which act against the benefit of most of their population to conspire with the content mafia.
Nice, thanks a lot, especially the dirty_bytes settings are interesting to me, because I experience hangs with too much disk IO :-P.
Cheers!
Could you ELI5 the last five settings? I saw that Chrome OS sets vm.overcommit_memory = 1, it seems to make sense but is missing here.
Thanks a lot! You are right, I saw this already.
I can confirm the findings with my benchmarks: zstd has the best compression, lz4 is the fastest.
To my understand it is swap read-ahead, and the number is a power for the base 2. This means the default reads 2^3 = 8 pages ahead. According to what I read, the default of 3 was set in the age of rotating discs and never adapted for RAM swap devices.
Thank you for the tip, I’ll check it out, if the Pi runs unstable again. Just surprised, it sounds that it happened often to you… Since I upgraded to better sd-cards, I never had sd-card trouble again for nearly a decade now. (And I am constantly running multiple Pis 24/7 as servers)