Chrismurphy (talk | contribs) mNo edit summary |
Chrismurphy (talk | contribs) No edit summary |
||
| Line 14: | Line 14: | ||
== What to test? == | == What to test? == | ||
Today's installment of Fedora Test Day will focus on testing the new '''[https://fedoraproject.org/wiki/Changes/SwapOnZRAM SwapOnZRAM]''' change set. | Today's installment of Fedora Test Day will focus on testing the new '''[https://fedoraproject.org/wiki/Changes/SwapOnZRAM SwapOnZRAM]''' change set. | ||
== Who's available? == | == Who's available? == | ||
| Line 24: | Line 24: | ||
== Prerequisites for Test Day == | == Prerequisites for Test Day == | ||
Any Fedora edition/spin: 31, 32, Rawhide. | |||
<span style=color:red>dnf install zram-generator</span></br > | |||
<span style=color:red>cp /usr/share/doc/zram-generator/zram-generator.conf.example /etc/systemd/zram-generator.conf</span></br > | |||
* Edit the copy of the config file, and insert:</br > | |||
<span style=color:red>[zram0]</span></br > | |||
<span style=color:red>memory-limit = none</span></br > | |||
<span style=color:red>zram-fraction = 0.5</span></br > | |||
Optional: <span style=color:red>dnf remove anaconda zram</span></br > | |||
The swap-on-zram implementations in these packages have minor conflicts with zram-generator, but mostly they'll just contribute to user confusion. | |||
== How to test? == | == How to test? == | ||
Simple memory hogging test: Open dozens of Firefox tabs, until memory and swap fill up. | |||
Optional: [https://github.com/sergey-senozhatsky/zram-perf-test zram performance testing toolset] This is a bit more complex to get setup and understand the results. But could be useful to confirm/deny the default compression algorithm: lzo-rle is a good default across many architectures and general purpose workloads. | |||
=== Run the tests === | === Run the tests === | ||
Revision as of 14:34, 12 June 2020
| Fedora Test Day | |
|---|---|
| |
| SwapOnZRAM | |
| Date | TBD |
| Time | all week |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's installment of Fedora Test Day will focus on testing the new SwapOnZRAM change set.
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - chrismurphy (cmurf), zbyszek
- Quality Assurance - Sumantro Mukherjee (sumantrom), Kamil Paral (kparal), Geoff (coremodule), Adam Williamson (adamw)
Prerequisites for Test Day
Any Fedora edition/spin: 31, 32, Rawhide.
dnf install zram-generator
cp /usr/share/doc/zram-generator/zram-generator.conf.example /etc/systemd/zram-generator.conf
- Edit the copy of the config file, and insert:
[zram0]
memory-limit = none
zram-fraction = 0.5
Optional: dnf remove anaconda zram
The swap-on-zram implementations in these packages have minor conflicts with zram-generator, but mostly they'll just contribute to user confusion.
How to test?
Simple memory hogging test: Open dozens of Firefox tabs, until memory and swap fill up.
Optional: zram performance testing toolset This is a bit more complex to get setup and understand the results. But could be useful to confirm/deny the default compression algorithm: lzo-rle is a good default across many architectures and general purpose workloads.
Run the tests
Reporting bugs
If you have problems with any of the tests, have a look in the results page. Please include the vulnerability output at the end of the test suite in the comments.
If you don't see it, please file a new bug to Bugzilla, probably against rust-zram-generator component. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.