zram-swap-config VS zram-generator

crontab, /etc/rc.local or create a simple systemctl service are all prob the easiest and most secure ways to allow on boot. /etc/rc.local I think happens after all services think `@reboot` with crontab is the same but you would have to google to be sure. or copy and hack the service from https://github.com/StuartIanNaylor/zram-swap-config as really they are also quite simple to create

I still have https://github.com/StuartIanNaylor/zram-swap-config but doesn't do much more than https://github.com/systemd/zram-generator#readme but I passed control of https://github.com/ecdye/zram-config as maintenance aint my strong point and it was just a protest of hey guys get this sorted.

I read in a few articles that the default sram-config package has some sizing/erro handling issues. Two configuration scripts seem to be recommended: this one and this other one.

zram can help as create a swap that the majority of time will be used also mounting a small zram zstd (great text compression) for var/log will practically bring writes to pretty much nothing. Armbian have a util that does that. You are using 62.2m 9very small) of 872m main memory Swap virtual memory you are using 40.8m of 100m because dphys-swap is set to only 100m by default but is just disk space. Its prob pushed 40.8m there because its idle so its pushed it out of main memory and will pull back if ever needed. I use my util https://github.com/StuartIanNaylor/zram-swap-config and another one I did is now maintained by openhab. Dunno if systemd/zram-generator is in raspberry might actually a great zram util.

zram when your confined with 512mb as sd card swap sucks. https://github.com/StuartIanNaylor/zram-swap-config zram isn't perfect as you will get apps that pass already compressed uncompressible data, but luckily is the exception not the rule and web based is usually highly compressable.

https://github.com/StuartIanNaylor/zram-swap-config just install and reboot

Remember to finish the installation and install zram-swap-config for global zram.

No, but should you want to enable it, you can install systemd-zram-generator.

See also: https://github.com/systemd/zram-generator

As someone else mentioned, for many cases this will be a performance increase, not decrease. Compressing infrequently used memory frees up more memory to be used for filesystem caching among other things.

if you are using zram generator you could edit the config file. why do you want more swap?

23.05 replaced the old zramSwap option with the new environment.systemPackages.pkgs.zram-generator package. The new package also requires a configuration file in /etc/systemd/zram-generator.conf.

To the file zram-generator.conf, if my memory don't fail this file is located at /usr/lib/systemd/zram-generator.conf, but I can be wrong. You can find more information on the fedora zram options and the zram-generator.conf location here: https://github.com/systemd/zram-generator

https://github.com/systemd/zram-generator/tree/main#readme

https://github.com/systemd/zram-generator There is a Debian package for it: https://packages.debian.org/bookworm/systemd-zram-generator

as u/anoobis2 said, what about your swap? I suggest you to use ZRAM it's a boon for this kind of issues. I've found zram-generator very easy to use, (just remember to disable zswap).

You can use zram-generator. It's very easy to setup! https://github.com/systemd/zram-generator

I had this exact issue. The few times I made it to character select before a crash and tried to log in, crashes would crop up if I teleported to a town, or logged out in one and tried logging back in. My system was running out of RAM and the game would crash. I had to set up a zram swap file and that solves all my crashes. I used zram-generator for this.