git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Utsav Shah <utsav@dropbox.com>
To: git@vger.kernel.org
Subject: Speeding up git stash - help needed
Date: Thu, 24 Oct 2019 20:05:11 -0700	[thread overview]
Message-ID: <CAPYzU3OEjjFgRrzAM04O3Dmg78FLo=n1X+EU-D_SoThKmiZtsA@mail.gmail.com> (raw)

There's been some work to improve the performance of commands using
fsmonitor to skip unnecessary lstats. This has worked wonderfully for
git status on our repository, and I'm trying to see if we can extend
that to more commands.

A profile of git stash on our repository shows a fair bit of time is
spent in the "git reset --hard" that happens at the end. Most of the
time there is spent running lstat in unpack-trees.c -> traverse_trees
-> oneway_merge, which is a fairly generic function and used in a few
places.

Is there a sane way to try skipping those lstats? Does anyone have an
approach they'd recommend? Or is it possible to skip the git reset
--hard in some way? Any suggestions would be welcome.

                 reply	other threads:[~2019-10-25  3:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPYzU3OEjjFgRrzAM04O3Dmg78FLo=n1X+EU-D_SoThKmiZtsA@mail.gmail.com' \
    --to=utsav@dropbox.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).