public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: andrew stern <astern.fix8.forum@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Possible issue with newest version of git (v 2.8) under Cygwin
Date: Tue, 10 May 2016 13:15:00 -0000	[thread overview]
Message-ID: <CADMefsZxMh4dtPJct0UzG3uFLQ9ea3NJcqcTrVtqmmzm-s6AMA@mail.gmail.com> (raw)

>I suspect this isn't a problem with the Git upgrade but with recent
>changes that have been being made to how the core Cygwin dll handles
>permissions.

>That being said, can you try running `git config core.filemode false` in
>the repository, re-enabling noacl, and see if that has things running at
>something more like normal speed?  That disables Git's checks on file
>permissions, so it should isolate whether the slow-down is specifically
>Git checking permissions or if merely accessing files is the problem.

>(With core.filemode disabled, you'll need to use `git update-index` to
>add/remove the executable flag on files in the Git repository; see `git
>help update-index` for details on how that works.  To undo the config
>change, use `git config core.filemode true`.)

This repository is created with the filemode=false after I finish
cloning from the repository using cygwin.
I've decided to try cygexec on the fstab to see if it helps and it
does seem much faster.
I don't know if this is the correct way to speed it up again but the
speed slow down does seem related to reading each file and determining
if it is executable.
The new line is:
none /cygdrive cygdrive binary,posix=0,user,noacl,cygexec 0 0

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2016-05-10 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 13:15 andrew stern [this message]
2016-05-10 13:29 ` Adam Dinwoodie
  -- strict thread matches above, loose matches on Subject: below --
2016-05-16 13:03 andrew stern
2016-05-16 12:51 andrew stern
2016-05-10 13:59 andrew stern
2016-05-14 12:04 ` Adam Dinwoodie
2016-05-14 12:34   ` Norton Allen
2016-05-09 18:34 andrew stern
2016-05-09 19:59 ` andrew stern
2016-05-10 13:01   ` Adam Dinwoodie

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=CADMefsZxMh4dtPJct0UzG3uFLQ9ea3NJcqcTrVtqmmzm-s6AMA@mail.gmail.com \
    --to=astern.fix8.forum@gmail.com \
    --cc=cygwin@cygwin.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.
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).