From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: "W. David Jarvis" <william.d.jarvis@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Reducing CPU load on git server
Date: Mon, 29 Aug 2016 23:31:27 +0200 [thread overview]
Message-ID: <1472506287.4265.36.camel@kaarsemaker.net> (raw)
In-Reply-To: <CAFMAO9wQD5GtGRGv-sMy=NA1q8kbu6n3FFbWuJ+W5-qnRDKW-w@mail.gmail.com>
On ma, 2016-08-29 at 13:57 -0700, W. David Jarvis wrote:
> > * If you do need branches consider archiving stale tags/branches
> > after some time. I implemented this where I work, we just have a
> > $REPO-archive.git with every tag/branch ever created for a given
> > $REPO.git, and delete refs after a certain time.
>
> This is something else that we're actively considering. Why did your
> company implement this -- was it to reduce load, or just to clean up
> your repositories? Did you notice any change in server load?
At 50k refs, ref negotiation gets expensive, especially over http
D.
prev parent reply other threads:[~2016-08-29 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 19:42 Reducing CPU load on git server W. David Jarvis
2016-08-28 21:20 ` Jakub Narębski
2016-08-28 23:18 ` W. David Jarvis
2016-08-29 5:47 ` Jeff King
2016-08-29 10:46 ` Jakub Narębski
2016-08-29 17:18 ` Jeff King
2016-08-29 19:16 ` W. David Jarvis
2016-08-29 21:31 ` Jeff King
2016-08-29 22:41 ` W. David Jarvis
2016-08-31 6:02 ` Jeff King
2016-08-30 10:46 ` git blame <directory> [was: Reducing CPU load on git server] Jakub Narębski
2016-08-31 5:42 ` Jeff King
2016-08-31 7:28 ` Dennis Kaarsemaker
2016-08-29 20:14 ` Reducing CPU load on git server Ævar Arnfjörð Bjarmason
2016-08-29 20:57 ` W. David Jarvis
2016-08-29 21:31 ` Dennis Kaarsemaker [this message]
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=1472506287.4265.36.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=william.d.jarvis@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://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).