This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Possible issue with newest version of git (v 2.8) under Cygwin


On Tue, May 10, 2016 at 09:15:48AM -0400, andrew stern wrote:
> >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

I'm not sure I understand what you're seeing: if your repository is
already set up with core.filemode set to false, Git won't check the
executable flag on the files.  What leads you to think the speed
slow-down is related to checking whether the file is executable?

If setting cygexec makes a noticable speed difference even with
core.filemode false, I can only conclude the problem is somewhere below
Git and related to how the Cygwin DLL provides file access.

FWIW, having just checked the Cygwin user guide's fstab instructions[0],
the noacl setting should be ignored on NFS filesystems; if you're seeing
that make a difference, that looks like a bug.

[0]: https://cygwin.com/cygwin-ug-net/using.html#mount-table

Adam

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]