Skip to content
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.

Can we cut a release please? #7

Open
spaetz opened this issue Sep 3, 2020 · 1 comment
Open

Can we cut a release please? #7

spaetz opened this issue Sep 3, 2020 · 1 comment

Comments

@spaetz
Copy link

spaetz commented Sep 3, 2020

Give Debian's old package which fails to use more than one core (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917643) it would be great to cut a new release, so that Debian can pick up the fixes that have happened on April 2, 2019.

@StuartIanNaylor
Copy link

StuartIanNaylor commented Sep 4, 2020

https://github.com/StuartIanNaylor/zram-config
https://github.com/StuartIanNaylor/zram-swap-config

Your still shy on function as the worst thing is you make zero checks for any existing zram services and just overwrite.
Also swap parameters are very much based on hdparms which is far from optimal use of memory.

Posted the above so you can see how to check for other services and how to set memory optimal parameters.

I have no idea why many default zram-tools miss some basic essential function.

Also any zram implementation doesn't fail to use more than one core as its multi-stream by default.

pi@raspberrypi:~ $ zramctl
NAME       ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lzo-rle     414.8M  50M 20.2M 21.6M       4 [SWAP]

As on a 4 core Pi.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants