From: Taylor Blau <me@ttaylorr.com>
To: Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, sluongng@gmail.com,
martin.agren@gmail.com, sunshine@sunshineco.com,
Derrick Stolee <derrickstolee@github.com>
Subject: Re: [PATCH 0/2] Maintenance: add pack-refs task
Date: Mon, 8 Feb 2021 17:46:55 -0500 [thread overview]
Message-ID: <YCG/X12qKVKu3/pv@nand.local> (raw)
In-Reply-To: <pull.871.git.1612795943.gitgitgadget@gmail.com>
On Mon, Feb 08, 2021 at 02:52:21PM +0000, Derrick Stolee via GitGitGadget wrote:
> I chose to add it to the incremental maintenance strategy at a weekly
> cadence. I'm not sure there is significant value to the difference between
> weekly and daily. It just seems to me that weekly is often enough. Feel free
> to correct me if you have a different opinion.
I don't have any strong opinion about this. At GitHub we run pack-refs
as part of a maintenance-like job, which varies in frequency between
different repositories based on a number of factors. In our busiest
repository networks, this is almost certainly at least a few times a
day, if not "as often as possible."
I'd suspect that for any laptop-sized repository, anywhere between daily
and weekly is just fine.
I suppose weekly is a good starting point, since we can always change
the default to run more often if enough users complain.
> My hope is that this patch series could be used as an example for further
> extracting tasks out of the gc task and making them be full maintenance
> tasks. Doing more of these extractions could be a good project for a new
> contributor.
That's great :-).
Thanks,
Taylor
next prev parent reply other threads:[~2021-02-08 22:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 14:52 [PATCH 0/2] Maintenance: add pack-refs task Derrick Stolee via GitGitGadget
2021-02-08 14:52 ` [PATCH 1/2] maintenance: " Derrick Stolee via GitGitGadget
2021-02-08 22:53 ` Taylor Blau
2021-02-09 12:42 ` Derrick Stolee
2021-02-08 23:06 ` Eric Sunshine
2021-02-09 12:42 ` Derrick Stolee
2021-02-08 14:52 ` [PATCH 2/2] maintenance: incremental strategy runs pack-refs weekly Derrick Stolee via GitGitGadget
2021-02-08 22:46 ` Taylor Blau [this message]
2021-02-09 13:42 ` [PATCH v2 0/2] Maintenance: add pack-refs task Derrick Stolee via GitGitGadget
2021-02-09 13:42 ` [PATCH v2 1/2] maintenance: " Derrick Stolee via GitGitGadget
2021-02-09 13:42 ` [PATCH v2 2/2] maintenance: incremental strategy runs pack-refs weekly Derrick Stolee via GitGitGadget
2021-02-10 2:41 ` [PATCH v2 0/2] Maintenance: add pack-refs task Taylor Blau
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YCG/X12qKVKu3/pv@nand.local \
--to=me@ttaylorr.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.com \
--cc=sluongng@gmail.com \
--cc=sunshine@sunshineco.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://80x24.org/mirrors/git.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).