Arch Linux User Repository

i've quicky hacked a new version. please try it out...

thanks for all the input. i'll be leaving tomorrow for a week but i'll try to look into this before i leave. otherwise, please be patient... ...also, always patches welcome! ;-)

Still does strange things like create multiple devices when zram is multi-stream by default.

Doesn't check for existing zram services and so will overwrite.

Also omits the mem_limit cap to control actual memory usage.

Irrespective of alg its still out of date.

I mean, if it hadn’t been changed to specifically use the non-default compression algorithm, upgrading the kernel to 5.1+ would automatically have made lzo-rle what was used by default… I don’t think the script should hardcode the compression method. If people want to use lz4, they can make it do so themselves. Trust that the kernel devs make informed decisions on what compression to use by default?

@rpodgorny

I have changed your config and I'm already trying lzo-rle with kernel 5.1:

$ cat /sys/block/zram0/comp_algorithm lzo [lzo-rle] lz4 lz4hc 842 zstd

$ zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram1 lzo-rle 480,6M 4K 79B 12K 2 [SWAP] /dev/zram0 lzo-rle 480,6M 4K 79B 12K 2 [SWAP]

Now I'm testing if really faster than lz4...

Hi rpodgorny,

as you asked me to advise you, Linux kernel 5.1 is finally available.

So now that lzo-rle compression is also available (https://www.phoronix.com/scan.php?page=news_item&px=ZRAM-Linux-5.1-Better-Perform), will you apply it to zramswap?

bump me when 5.1 is out. also, please remove the package deletion request. thank you...

Hi there, now that lzo-rle compression will be available (https://www.phoronix.com/scan.php?page=news_item&px=ZRAM-Linux-5.1-Better-Perform), will you apply it to zramswap? Bye, thanks.

Its great that you have made a package for Arch problem is you have used zram-config-0.5.deb as a basis.

Afraid much of what you are doing like creating devices per core whilst zram is multi-stream by default is purely through the Chinese bad whispers of the above package. You use the pointless num_devices which is optional and don't check if any exist say for the likes of log2ram. Zram is a hotplug system like zramctl --find find a free device I have been on a rant to Ubuntu about how a package such as the above has passed so many release when it is practically broken in every way and somehow manages to encourage so many copies.

Read the kernel doc and you find there is little correlation. https://www.kernel.org/doc/Documentation/blockdev/zram.txt You can check my repo out which prob needs pollish but at least is relatively correct. https://github.com/StuartIanNaylor/zram-swap-config

Read the bugs and my questions on what is obviously your source. https://launchpad.net/ubuntu/+source/zram-config/+bugs

PS log2ram is also great and if your updating packages and maybe in the mood have a look at. https://github.com/StuartIanNaylor/log2ram

Needs a config script as disk_size, mem_limit and the choice of any comp alg from /proc/crypto is far to wide a choice to be hard wired.

I have noticed that there is little difference on some distribs between lzo & lz4 and thinking it might be down to binary optimisation and in many cases where this is used if NEON optimisation has been implemented in compile. lz4 should be much faster but seems in use much less than expected with raspian that is. Prob Arch haven't checked lz4 should be a clear winner.