From: Duy Nguyen <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: Git Mailing List <email@example.com>, Junio C Hamano <firstname.lastname@example.org>, Jeff King <email@example.com> Subject: Re: [PATCH/RFC] gitperformance: add new documentation about git performance tuning Date: Wed, 5 Apr 2017 19:56:40 +0700 [thread overview] Message-ID: <CACsJy8AQjBZcpPCUNMhVNo33C4PCeFMbJhg31LfYEH+wA27ntw@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Tue, Apr 4, 2017 at 4:16 AM, Ævar Arnfjörð Bjarmason <email@example.com> wrote: > Things I have on my TODO list: Always keep cache-tree valid. I think there's some changes in "git checkout" to rebuild cache-tree often, so it's probably not as bad as before. I don't know if there's a command to manually repair cache-tree after it's damaged too much (or even better, attempt to repair cache-tree automatically once damages go over a limit, similar to how you automatically split index). > +git status > +~~~~~~~~~~ > + > +Running "git status" requires traversing the working tree & comparing > +it with the index. Several configuration options can help with its > +performance, with some trade-offs. Another option, if you know you only make changes in one (preferably deep) subdirectory and your whole worktree is very large, then you could do something like "git status .". This speeds git-status up a bit because it won't need to look outside (or speeds up a lot if "outside" is very large). The con is, changes outside "." will not be seen. -- Duy
prev parent reply other threads:[~2017-04-05 12:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-03 21:16 Ævar Arnfjörð Bjarmason 2017-04-03 21:34 ` Eric Wong 2017-04-03 21:57 ` Ævar Arnfjörð Bjarmason 2017-04-03 22:39 ` Eric Wong 2017-04-04 21:12 ` Ævar Arnfjörð Bjarmason 2017-04-04 2:19 ` Jeff King 2017-04-04 15:07 ` Jeff Hostetler 2017-04-04 15:18 ` Ævar Arnfjörð Bjarmason 2017-04-04 18:25 ` Jeff Hostetler 2017-04-05 12:56 ` Duy Nguyen [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=CACsJy8AQjBZcpPCUNMhVNo33C4PCeFMbJhg31LfYEH+wA27ntw@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH/RFC] gitperformance: add new documentation about git performance tuning' \ /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
Code repositories for project(s) associated with this 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).