all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Christian Faulhammer <fauli@gentoo.org>
Cc: emacs@gentoo.org, Joakim.Tjernlund@transmode.se, emacs-devel@gnu.org
Subject: Re: Slow start-up on Git trees
Date: Wed, 19 Aug 2009 13:56:00 -0700 (PDT)	[thread overview]
Message-ID: <200908192056.n7JKu0Bv001763@godzilla.ics.uci.edu> (raw)
In-Reply-To: <20090819132341.3f2dddc5@gentoo.org> (Christian Faulhammer's message of "Wed, 19 Aug 2009 13:23:41 +0200")

Christian Faulhammer <fauli@gentoo.org> writes:

  > Hi,
  > 
  > Joakim Tjernlund reported in
  > http://bugs.gentoo.org/show_bug.cgi?id=281009 that Emacs started in a
  > Git tree is really slow.  This does not happen with other SCM systems
  > and we were able to reproduce the problem and narrowing it down
  > to /usr/bin/git diff-index -z HEAD -- Makefile, called in
  > vc-git-state.  Any possibilities to improve performance here?

There are at lease two ways: 
- talk the git people to improve the performance of "git diff-index",
- implement a vc-git-state-heuristic (see other vc-*-state-heuristic
  functions) that parses .git/index and uses that return the state of
  the file, thus avoiding the "git diff-index" call.

Is worth it?  
I'd say probably not, the delay only happens the first time of accessing
a file in the git tree.




  reply	other threads:[~2009-08-19 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 11:23 Slow start-up on Git trees Christian Faulhammer
2009-08-19 20:56 ` Dan Nicolaescu [this message]
2009-08-19 21:04   ` David Reitter
2009-08-19 21:11     ` Dan Nicolaescu
2009-08-20 18:46       ` David Reitter
2009-08-20 19:15         ` Dan Nicolaescu
2009-08-21 19:06           ` Stefan Monnier
2009-08-19 21:54   ` Christian Faulhammer
2009-08-20  7:39   ` Joakim Tjernlund
2009-08-20  8:07     ` Dan Nicolaescu

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=200908192056.n7JKu0Bv001763@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=Joakim.Tjernlund@transmode.se \
    --cc=emacs-devel@gnu.org \
    --cc=emacs@gentoo.org \
    --cc=fauli@gentoo.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.