Might be late to the party, but I just discovered you can do this. Super simple and easy to do.
After having a read of the linked page, I backed up and just used this option:
https://wiki.archlinux.org/title/Profile-sync-daemon
Installed, created config, and enabled service:
systemctl --user enable psd.service systemctl --user enable psd-resync.service
I definitely notice an increase in speed and less SSD usage should hopefully increase lifespan.
I’m sure there would be options for alternative distros, anything using Systemd should be able to use the daemon.
Finally, a way to use the loads of RAM I have other than Compiling and Blendering.
Well, I guess we also have RAM drives
Just reconfigured /etc/makepkg.conf to use extra cores and tmpfs… I’ve been compiling on the SSD with one core for so long it’s embarrassing.
While you’re still in your makepkg.conf, don’t forget to set
march=native(and remove mtune) in yourCFLAGS! (unless you’re sharing your compiled packages with other systems)Where’s the difference between
march=nativeandmarch=x86-64in that case?A ton of difference!
marchstands for microarchitecture levels (or feature levels). “x86-64” is the baseline feature set targeting common x86_64 instructions found in early 64-bit CPUs, circa 2003. Since 2003 obviously there have been several advancements in CPUs and the x86_64 arch, and these have been further classified as:So if you’re still on x86-64, you’re missing out on some decent performance gains by not making use of all the newer instructions/optimisations made in the past two decades(!).
If you’re on a recent CPU (2017+), ideally you’d want to be on at least x86-64-v3 (v4 has seemingly negligible gains, at least on Intel). There’s also CPU-family specific marches such as
znver4for AMD Zen 4 CPUs, which would be an even better choice than x86-64-v4.But the best march you want use is of course
native- this makes available all instructions and compiler optimisations that’s specific to your particular CPU, for the best performance you can possibly get. The disadvantage ofnativeis that any binaries compiled with this can run only on your CPU (or a very similar one) - but that’s only an issue for those who need to distribute binaries (like software developers), or if you’re sharing your pkg cache with other machines.Since the flags defined in makepkg.conf only affect AUR/manual source builds (and not the default core/extra packages), I’d recommend also reinstalling all your main packages from either the ALHP or CachyOS repos, in order to completely switch over to x86-64-v3 / v4.
Further reading on microarchitectures:
Benchmarks:
cc: @luthis@lemmy.nz
Oh boy…
Total Download Size: 3390.65 MiB Total Installed Size: 13052.08 MiB Net Upgrade Size: 291.24 MiB
I wonder if I’m going to notice any better performance…
Can I also compile a list of selected packages from the repositories fresh easily? E.g. Firefox? Or do I have to download their PKGBUILD to makepkg?
The repositories already contain pre-compiled packages. To install them, just add the repository before the Arch repos, and then simply reinstall the packages to install their optimised versions.
How can I trust them? At least with Arch there’s the “many eyes” principle.
It’s the same principle. Both CachyOS and ALHP are reasonably popular, and all their stuff is open for anyone to review - Cachy’s stuff is all on Github and ALHP is on SomeGit.
holy shit!!! I’m definitely doing that!
Mount .cache as tmpfs. Rarely needs a workaround for some offenders to XDG spec though.