git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: Nathan and Ila Reynolds <nathanila@gmail.com>, git@vger.kernel.org
Subject: Re: Cygwin Git Performance
Date: Tue, 21 May 2019 17:06:01 -0400	[thread overview]
Message-ID: <5d06cf4a-c29f-335f-52f9-c6c35369b673@jeffhostetler.com> (raw)
In-Reply-To: <01cf52cb-7e90-efde-a06c-f0413f9efc8a@gmail.com>



On 5/21/2019 10:34 AM, Nathan and Ila Reynolds wrote:
> I am not sure if this is the right mailing list.  If not, please 
> redirect me to the right place.
> 
> I have Cygwin's git (2.21.0) and Git for Windows (2.21.0) installed on 
> my Windows 10 machine.  I run the following command with each binary 
> "git push --all" on a simple 2 line change to 1 file.  If I use Cygwin's 
> git, then the operation takes almost 5 minutes.  If I use Git for 
> Windows, then the operation takes almost 20 seconds.  I tried using 
> --verbose to figure out why Cygwin's git is so slow but it does not 
> reveal anything to me as to why.  What can I do to figure out why 
> Cygwin's git is so slow? I am hoping that we can get to the bottom of 
> this and it can be fixed to help all users.
> 


You might try turning on GIT_TRACE_PERFORMANCE [1] and see if that
shows any differences.

If you can install 2.22.0-rc* versions of both, you can turn on
GIT_TR2_PERF [2] and some additional details.

If your repo is very large, it may be due to some Windows file system
optimizations present in the Git for Windows version.

[1] https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables
[2] 
https://github.com/git/git/blob/master/Documentation/technical/api-trace2.txt#L80


Hope that helps,
Jeff

      parent reply	other threads:[~2019-05-21 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 14:34 Cygwin Git Performance Nathan and Ila Reynolds
2019-05-21 14:47 ` Adam Dinwoodie
2019-05-21 21:06 ` Jeff Hostetler [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=5d06cf4a-c29f-335f-52f9-c6c35369b673@jeffhostetler.com \
    --to=git@jeffhostetler.com \
    --cc=git@vger.kernel.org \
    --cc=nathanila@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).