Package Details: zramswap 2-1

Git Clone URL: https://aur.archlinux.org/zramswap.git (read-only)
Package Base: zramswap
Description: Sets up zram-based swap devices on boot
Upstream URL: http://en.wikipedia.org/wiki/ZRam
Licenses: GPL
Submitter: Svenstaro
Maintainer: rpodgorny
Last Packager: rpodgorny
Votes: 215
Popularity: 1.182902
First Submitted: 2011-10-05 23:35
Last Updated: 2018-03-18 23:48

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

rpodgorny commented on 2019-03-15 13:47

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

papakilo commented on 2019-03-15 08:34

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.

stuartiannaylor commented on 2019-03-14 13:48

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.

jaab commented on 2018-04-13 10:46

Works like a charm for small arm devices. Thank you!

duffydack commented on 2018-03-19 00:13

/dev/zram{0-7} lz4 199.2M 4K 68B 4K 8 [SWAP]

Excellent, thank you.

rpodgorny commented on 2018-03-18 23:56

updated. please test.

duffydack commented on 2018-03-18 23:35

Lz4 is faster apparently, also arch wiki zram example. I can set it myself, it's no biggie.

rpodgorny commented on 2018-03-18 23:09

i'm not forcing any particular algorithm so the default is being used. ...which seems to be lzo.

any reason why i should override the default?

duffydack commented on 2018-03-18 22:43

Any chance the script can set the algorithm to lz4. I can do this myself if need be, but think it's a good default to have using this PKG. Regards

rpodgorny commented on 2017-11-19 22:42

i don't think it's outdated. it's just a simpler version if you want zram only.