From: Jaco Kroon <jaco@uls.co.za>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] mirror storage growth rate
Date: Fri, 15 Mar 2024 10:06:36 +0200 [thread overview]
Message-ID: <57119c8c-24bd-49b0-b3a1-1ff31113e7f8@uls.co.za> (raw)
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
Hi All,
I was messing with some storage related caching on some of our hosts
this morning when I wondered about how much storage the gentoo mirrors
were consuming. I'm not too worried about the current storage, but I am
noticing that the storage requirements are creeping quite a bit (as per
attached), and if that growth rate continues it may become a problem
*eventually*.
Can this growth be explained?
Is it expected to continue at this rate?
Kind regards,
Jaco
[-- Attachment #2: gentoo_mirror_storage.png --]
[-- Type: image/png, Size: 3244 bytes --]
next reply other threads:[~2024-03-15 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 8:06 Jaco Kroon [this message]
2024-03-15 12:05 ` [gentoo-dev] mirror storage growth rate Michał Górny
2024-03-15 15:40 ` Hoël Bézier
2024-03-15 16:15 ` Maciej Barć
2024-03-15 18:21 ` Andreas K. Huettel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57119c8c-24bd-49b0-b3a1-1ff31113e7f8@uls.co.za \
--to=jaco@uls.co.za \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox