On Wed, Sep 18, 2019 at 6:57 PM Tom Seewald wrote:
>
> Hi Chris,
>
> Does zswap actually keep the data compressed when the DRAM-based swap is
> full, and it writes to the spill-over non-volatile swap device?
>
> I'm not an expert on this at all, however my understanding was that zswap
> must dec
Hi Chris,
Does zswap actually keep the data compressed when the DRAM-based swap is full,
and it writes to the spill-over non-volatile swap device?
I'm not an expert on this at all, however my understanding was that zswap must
decompress the data before it writes to the backing swap. But perhap
Zbyszek,
Do you have any advice on how to assess 'swap on ZRAM' versus 'zswap'
by default for Fedora Workstation? They're really too similar from a
user point of view, I think it really comes down to the technical
arguments.
1a. 'swap on ZRAM' compresses only that which goes to the ZRAM device
1b
Hi,
thank you for all the testing and comparisons between different
approaches. It looks really interesting.
> The ideal scenario is to get everyone on the same page, and so far it
> looks like systemd's zram-generator, built in Rust, meets all the
> requirements. That needs to be confirmed, but
On Fri, Aug 30, 2019 at 1:55 PM Chris Murphy wrote:
>
> Hi,
> This is yet another follow-up for this thread:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XUZLHJ5O32OX24LG44R7UZ2TMN6NY47N/
(Benchmarks being fraught with peril, synthetic benchmarks even mo
- Original Message -
> From: "Chris Murphy"
> To: "Development discussions related to Fedora"
>
> Sent: Friday, August 30, 2019 9:55:52 PM
> Subject: swap on ZRAM, zswap, and Rust was: Better interactivity in
> low-memory situations
>
>
Hi,
This is yet another follow-up for this thread:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XUZLHJ5O32OX24LG44R7UZ2TMN6NY47N/
Basics:
"zswap" compresses swap and uses a defined memory pool as a cache,
with spill over (still compressed) going into a conve
