[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Btrfs by default, the compression option
From:       Chris Murphy <lists () colorremedies ! com>
Date:       2020-07-10 6:59:37
Message-ID: CAJCQCtRYWVKoS3sFHameZcAfnNpXwepuzR6RCjz5uFgJ2UYx3w () mail ! gmail ! com
[Download RAW message or body]

On Wed, Jul 8, 2020 at 9:50 AM Matthew Miller <mattdm@fedoraproject.org> wrote:
>
> More data is always better. I like qualifying the situations in that way. I
> think we should make our decision based on the "center" rather than the
> edges, though.
>
> For I hope obvious reasons, I'd love to see this tested on a Lenovo X1
> Carbon Gen 8 with the default SSD options.
>
> And, for benchmarks, I'm thinking more application benchmarks than a
> benchmark of the compression itself. How much does compressed /usr affect
> boot times for GNOME and KDE? What about startup time for LibreOffice,
> Firefox, etc? Any impact on run-time usage?

https://paste.centos.org/view/f4165396

Two workloads: install and update. It might seem like an update is
both read and write dependent, but the rpms are already compressed and
don't get compressed again. The differences, I expect, are mostly
write performance. And this suggests it's a wash. I'd say this setup
is fairly middle of the pack.

The space savings, however, isn't a wash.


-- 
Chris Murphy
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[prev in list] [next in list] [prev in thread] [next in thread]