From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: "Jonathan Brielmaier" <jonathan.brielmaier@web.de>,
"Ludovic Courtès" <ludo@gnu.org>,
40236@debbugs.gnu.org,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition.
Date: Fri, 10 Apr 2020 11:04:17 +0200 [thread overview]
Message-ID: <87eesvvhim.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20200410082425.GA1518@E5400>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Efraim Flashner <efraim@flashner.co.il> writes:
> On Fri, Apr 10, 2020 at 09:39:18AM +0200, Pierre Neidhardt wrote:
>> > So compression saves me 26% ([69-51]/69), and deduplication saves me
>> > 62% ([180-69]/180).
>>
>> Thanks for sharing!
>> zstd might give better results. Any reason you chose lzo over zstd?
>>
>
> My machine is about 10 years old so I was more concerned than normal
> about the CPU usage. If lz4 was an option I would've gone with that, but
> according to the Arch wiki or some other locations lzo was basically the
> fastest option.
I've tried zstd on an AMD Athlon II X4 635 (2010): it's perfectly
smooth, can't notice any performance drop. In fact, I wonder if it's
not even faster than before, but it's hard to measure.
Note that Arch Wiki tends to be on the conservative side when it comes
to performance. I would not use it as a reference for the general case:
it may guide users to sacrifice convenience and features over
unnoticeable performance gains.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-10 9:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 8:35 [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition Pierre Neidhardt
2020-03-31 1:52 ` Maxim Cournoyer
2020-03-31 7:52 ` Pierre Neidhardt
2020-03-31 14:53 ` Pierre Neidhardt
2020-03-31 23:20 ` Maxim Cournoyer
2020-04-01 7:00 ` Pierre Neidhardt
2020-05-02 13:29 ` Pierre Neidhardt
2020-05-02 13:50 ` Marius Bakke
2020-05-02 13:58 ` Pierre Neidhardt
2020-05-02 19:03 ` Maxim Cournoyer
2020-05-03 7:01 ` Pierre Neidhardt
2020-05-04 15:22 ` Maxim Cournoyer
2020-04-01 21:28 ` Ludovic Courtès
2020-04-02 7:15 ` Pierre Neidhardt
2020-04-02 8:04 ` Ludovic Courtès
2020-04-02 10:36 ` Jonathan Brielmaier
2020-04-04 1:28 ` Maxim Cournoyer
2020-04-06 20:20 ` Pierre Neidhardt
2020-04-06 20:42 ` Jonathan Brielmaier
2020-04-07 7:07 ` Pierre Neidhardt
2020-04-08 3:18 ` Maxim Cournoyer
2020-04-09 20:12 ` Efraim Flashner
2020-04-10 7:39 ` Pierre Neidhardt
2020-04-10 8:24 ` Efraim Flashner
2020-04-10 9:04 ` Pierre Neidhardt [this message]
2020-04-14 2:20 ` Maxim Cournoyer
2020-04-14 6:53 ` Pierre Neidhardt
2020-05-31 7:39 ` Pierre Neidhardt
2020-05-31 7:55 ` Efraim Flashner
2020-06-01 4:21 ` Maxim Cournoyer
2020-06-01 6:16 ` Efraim Flashner
2020-06-01 7:48 ` Pierre Neidhardt
2020-06-01 18:29 ` Maxim Cournoyer
2020-05-31 21:07 ` Ludovic Courtès
2020-06-01 5:03 ` Maxim Cournoyer
2020-06-02 13:37 ` Pierre Neidhardt
2020-06-03 20:00 ` bug#40236: " Ludovic Courtès
2020-06-04 9:17 ` [bug#40236] " Pierre Neidhardt
2020-06-01 4:49 ` Maxim Cournoyer
2020-03-31 12:09 ` Jonathan Brielmaier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eesvvhim.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=40236@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jonathan.brielmaier@web.de \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).