From: Mathieu Othacehe <othacehe@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 51787@debbugs.gnu.org
Subject: bug#51787: Disk performance on ci.guix.gnu.org
Date: Mon, 20 Dec 2021 22:53:45 +0100 [thread overview]
Message-ID: <87a6gv3pue.fsf@gnu.org> (raw)
In-Reply-To: <871r27p5jq.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 20 Dec 2021 18:05:08 +0100")
Hey,
> Do you mean time the copy or time the removal from that storage? You
> know what, I’ll time both. I’ll need to get more space first. I think
> the trash directory is larger than the 500G that I got for testing the
> SAN.
Yeah I meant removal time :) I found this article[1] that suggests that
over time the ext4 fragmentation can cause a performance drop that is
very noticeable on hard drives.
I'm trying to determine how fragmented is the sdb1 file-system, by
running e4defrag and e2freefrag[2], but I'm not sure if they will
complete soon.
Copying and removing /gnu/store/trash on the SAN will be interesting but
the ultimate test would be to be able to re-create the ext4 file-system
directly on Berlin's sdb drive to evaluate the fragmentation role in
this funny business.
Thanks,
Mathieu
[1]: https://www.usenix.org/system/files/hotstorage19-paper-conway.pdf
[2]: https://cromwell-intl.com/open-source/performance-tuning/file-systems.html
next prev parent reply other threads:[~2021-12-20 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875yrjpi1y.fsf@elephly.net>
2021-12-20 16:59 ` bug#51787: Disk performance on ci.guix.gnu.org Mathieu Othacehe
2021-12-20 17:05 ` Ricardo Wurmus
2021-12-20 21:53 ` Mathieu Othacehe [this message]
2021-12-21 17:26 ` Ricardo Wurmus
2021-12-21 17:51 ` Leo Famulari
2021-12-21 18:23 ` Mathieu Othacehe
2021-12-21 23:20 ` Bengt Richter
2021-12-22 0:27 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-12-25 22:19 ` Ricardo Wurmus
2021-12-26 8:53 ` Mathieu Othacehe
2021-12-30 10:44 ` Ricardo Wurmus
2021-12-20 18:36 ` Bengt Richter
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=87a6gv3pue.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=51787@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).