On Jul 2, 1:06 am, Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> On Sunday, July 1, 2012 6:19:28 AM UTC+2, jack sparrow wrote:
> > On Jun 30, 1:13 am, Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> > > On Friday, June 29, 2012 2:29:59 PM UTC+2, jack sparrow wrote:
> > > > On Jun 29, 3:36 pm, Thomas Ferris Nicolaisen <tfn...@gmail.com>
> > wrote:
> > > > > It is possible to place a .gitignore file in each directory, and Git
> > > > will
> > > > > respect this. Therefore it checks every folder for this file, but I
> > > > doubt
> > > > > that's what is causing your performance problems.
> > > > > Can you please describe the size, number of files, and what kinds of
> > > > files
> > > > > there are in your repository?
> > > > > What is your Git version, and operating system?
> > > > the repo has around 80K files, git version 1.7.10-rc4 and operating
> > > > system is Linux.
> > > > the rep has just text based source files like .c,h, mk etc
> > > This sounds weird. I think I've had much better performance with larger
> > > repositories.
> > > I'm tending towards thinking it could maybe be some bug in that version
> > you
> > > have installed. It looks like a release-candidate (rc4), and could
> > > therefore be an unstable version. Have you tried other versions of Git?
> > > There are some interesting observations and discussions on huuuge
> > > repositories here<
> > > but I don't think you should be running into those problems.
> > ok, is there a way to know what is taking time.
> > any debugs in git, any profiling, there should be
> > someway of figuring out what git might be doing ...?
> You can do:
> GIT_TRACE=1;git status
> As I said earlier, you should try a version of Git which is not a
> You should also see how it performs on some different repositories:
> * Try another repository which is a bit smaller, both in number of files,
> size and number of revisions
> * Initialise your source tree as a new repo with no history, and see if it
> suffers the same performance problems
> Oh, another thing: What sort of hard-drive and file-system do you have? Are
> you working on an encrypted partition?
i tried with git version 126.96.36.199, the issue still remains,
this is a build repo from my organisation,
unfortunately i can't replicate the build
with that many files. GIT_TRACE is not helping
either, it just throws the following line.
trace: built-in: git 'status'
are there any verbose debugs that i can enable during
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at