It looks like this was finally properly addressed in 0.7, available
since Ubuntu 22.04/jammy, see https://launchpad.net/ubuntu/+source/zram-
config/+changelog
** Changed in: zram-config (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a memb
** Changed in: zram-config (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
zram-config fails to start/install on a system with more then 30
[Expired for zram-config (Ubuntu) because there has been no activity for
60 days.]
** Changed in: zram-config (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I updated zram-config package with chase9 patch and uploaded it to my test PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/test/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
@chase9 : your tests compared default zram-config vs. your customized
zram-config.
However, as you noticed, default zram-config already enabled multiple streams
for every device. Probably this is by accident, since multiple streams were
added by default in the kernel after zram-config package al
@chase9 : thanks for testing!
Would you like to also test performance with different compression algorithms?
See bug 1856043.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
zram-confi
ubuntu-release has been subscribed to this bug, but I don't see why.
This is not a well-formed feature freeze exception request, and it looks
like the issue here is a bug, not a new feature.
** Changed in: zram-config (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notif
This was tested in a VM running Ubuntu Server 20.04 with fewer than 29
cores dedicated to it, so I didn't run into the bug. Unfortunately the
production server wasn't available for testing (especially since each
benchmark took over an hour!).
Yes, custom zram-config means the sram-config but with
How were you able to enable "default zram-config" if it has this bug?
What do you mean exactly with "custom zram-config"? Just adding your
99_fixcores.patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Be sure to click the last link, as it will show you all three tests
side-by-side.
Overall, I would say that the custom zram-config doesn't much matter to
the performance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Here it is with the customized zram-config
https://openbenchmarking.org/result/2009143-FI-SWAP4713310
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
zram-config fails to start/install
Here is a benchmark with the default zram-config
https://openbenchmarking.org/result/2009144-FI-SWAP6511210
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
zram-config fails to start/i
Running benchmarks now. I'll upload as they get done. Here's the
baseline (stock Ubuntu Server install):
https://openbenchmarking.org/result/2009148-FI-SWAP7694110
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Unfortunately I only have a vague idea that I tested multi-stream, but then
reverted to multiple devices because of the poor performance.
Probably I just tested one of my scripts I use for managing my own stuff,
something that used a lot of CPU and RAM.
Don't remember anything else, sorry. :(
--
I can test this tonight on my Ubuntu server. Otherwise, I can test now
on a Fedora workstation. Do you have any tips for benchmarking swap?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
Before using multiple streams it would be nice to test the performance
(IIRC I did some test many years ago, and it scaled worse than having
multiple devices, but not really sure if my test was actually reliable
and eventually if that still applies with a recent kernel).
--
You received this bug
It's worth noting the multiple streams Oibaf mentioned are currently the
default. On my system, there are the max number of swap devices each
with 32 streams. I propose we only have one device and use the default
behavior of max_comp_streams = number of CPUs.
It's my first time creating an apt pat
I have 40 core machines, but I only get /dev/zram0 .. 25 used.
# lsb_release -d
Description:Ubuntu 18.04.1 LTS
# systemctl --all --failed
UNITLOAD ACTIVE SUBDESCRIPTION
Ï zram-config.service loaded failed
Note that with kernel 3.15, this should be revised. 3.15 indeed support
multi-stream functionality:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=beca3ec71fe5490ee9237dc42400f50402baf83e
It is no longer needed to set up many devices, just use 1 device and the use
som
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zram-config (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078165
Title:
The attachment "zram-config.conf.patch" of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'pat
21 matches
Mail list logo