| Hrrm. My comment was supoptimal, I guess. By "Not even insane amounts of RAM, it usually takes about 4 to 5GB, rarely going to 8, then shrinking back a while after closing too much tabs." I meant to say that this applies to the resident size in RAM of the whole browser, not what PSD does, or adds. That would be just what your browser profile is using 'on disk'. Peanuts, so to speak. With only 8GB it's really hard to tell. It depends on your usage patterns. First, regarding just PSD, it relies on RuntimeDirectorySize= of https://man.archlinux.org/man/logind.conf.5 which by default is limited to use up to 10% of system memory, but not statically reserved, only "on demand". Which in turn relies on tmpfs which can use up to half of system RAM by default. Again, on demand only, not statically reserved. https://wiki.archlinux.org/title/Tmpfs
https://wiki.gentoo.org/wiki/Tmpfs However, I think these are the wrong knobs to turn :-) PSD can make use of overlayfs, which saves a little bit of used RAM, and is faster to initially sync, but uses more disk space then. But not that much. Which can be further minimized by the number of kept profile backups, or not using backups at all. Just keep your profile lean and mean, then there's less stuff to shuffle around.
Since your'e using Vivaldi, pointing you to wikipages how to make Firefox use less RAM seems pointless ;) Maybe (carefully) use something like https://www.bleachbit.org for cleaning up Vivalidis profile. Which leaves things like https://en.wikipedia.org/wiki/Zram
https://wiki.archlinux.org/title/Zram
https://wiki.gentoo.org/wiki/Zram
https://www.kernel.org/doc/html/latest/admin-guide/blockdev/... OR https://en.wikipedia.org/wiki/Zswap
https://wiki.archlinux.org/title/Zswap
https://wiki.gentoo.org/wiki/Zswap
https://docs.kernel.org/admin-guide/mm/zswap.html to consider. While it may seem insane to reserve already limited RAM for just another thing, these are worth it. If configured right. I used them, or their predecessors since olden times, when I've just had a Thinkpad T60p with some Centrino and only 4GB. That made things better in general. Of course it's no silver bullet for everything, but it made the system less sluggish, and it took longer to slow down because of being 'swapped to death'. From then on I continued to use stuff like that. On a system with only 8GB, too. ZRAM in this case, because backing device like zswap was impossible, because the HDD blew. So I booted live from USB(2(Arrgh!)) and ran from RAM. By means of AntiX, which btw. showed my the ways sysctls regarding swappiness, pressure stall information, and related stuff can totally change the behaviour of a system. Even if it looks strange/ghettoish at first, which can be remastered away easily anyways, the devs really know how to get the most out of older systems with limited RAM and power, in interesting ways. Should be looked at, even if only for 'inspiration', technically. For instance making things like Firefox shrink back, after having closed too much tabs.
And remaining usable, while doing so. Anyway. Depending on what you do, 8GB only can go a looong way, if configured/used right. IMO not using ZRAM/ZSWAP, sysctls for swappiness, PSI, etc. is wrong and wasteful. PSD is just a little icing on the cake. |