From: "W. David Jarvis" <william.d.jarvis@gmail.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Reducing CPU load on git server
Date: Sun, 28 Aug 2016 16:18:03 -0700 [thread overview]
Message-ID: <CAFMAO9x5hi=drGSZTrJAxntjN+BATLCa_mSsqYZs+o6BO=x2wA@mail.gmail.com> (raw)
In-Reply-To: <51205109-5293-3058-f029-0703c33e8cb9@gmail.com>
My assumption is that pack bitmaps are enabled since the primary
server is a GitHub Enterprise instance, but I'll have to confirm.
On Sun, Aug 28, 2016 at 2:20 PM, Jakub Narębski <jnareb@gmail.com> wrote:
> W dniu 28.08.2016 o 21:42, W. David Jarvis pisze:
>
>> The ultimate goal for us is just figuring out how we can best reduce
>> the CPU load on the primary instance so that we don't find ourselves
>> in a situation where we're not able to run basic git operations
>> anymore.
>
> I assume that you have turned on pack bitmaps? See for example
> "Counting Objects" blog post on GitHub Engineering blog
> http://githubengineering.com/counting-objects/
>
> There are a few other articles there worth reading in your
> situation.
> --
> Jakub Narębski
--
============
venanti.us
203.918.2328
============
next prev parent reply other threads:[~2016-08-28 23:18 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 [this message]
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
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='CAFMAO9x5hi=drGSZTrJAxntjN+BATLCa_mSsqYZs+o6BO=x2wA@mail.gmail.com' \
--to=william.d.jarvis@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).