From: "T. V. Raman" <raman@users.sourceforge.net>
Subject: Suggestion: vc-hooks.el: Make vc-handled-backends more conservative?
Date: Mon, 9 Oct 2006 18:44:55 -0700 [thread overview]
Message-ID: <17706.64279.627316.725306@gargle.gargle.HOWL> (raw)
In vc-hooks.el, vc-handled-backends
is presently declared to handle a large number of backends:
(defcustom vc-handled-backends '(RCS CVS SVN SCCS Arch MCVS)
The last two --arch and MCVS have a particularly bad performance
penalty on systems that have NFS mounts in places other than /net
or /afs --- se variable vc-ignore-dir-regexp
Unless one discovers the above variable (vc-ignore-dir-regexp is
declared as a defvar, and not as defcustom)
nfs based systems take a heavy performance hit --- since function
vc-find-root recursively ascends the directory tree in attempting
to check if files are under version control.
Suggestions:
A) Possibly make vc-handled-backends more conservative by pruning
it to have RCS CVS and SVN on it by default.
B) Make vc-ignore-dir-regexp a customizable option via
defcustom,
and add a pointer to it in the docstring for
vc-handled-backends so that users discover its purpose
In my case I chased it down by examining the source code
after observing that emacs was making excessive nfs
accesses during file load and save.
--
Best Regards,
--raman
Email: raman@users.sf.net
WWW: http://emacspeak.sf.net/raman/
AIM: emacspeak GTalk: tv.raman.tv@gmail.com
PGP: http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman
IRC: irc://irc.freenode.net/#emacs
next reply other threads:[~2006-10-10 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 1:44 T. V. Raman [this message]
2006-10-10 3:23 ` Suggestion: vc-hooks.el: Make vc-handled-backends more conservative? Stefan Monnier
2006-10-11 13:28 ` T. V. Raman
2006-10-11 18:28 ` Stefan Monnier
2006-10-13 1:31 ` T. V. Raman
2006-10-13 5:23 ` Stefan Monnier
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17706.64279.627316.725306@gargle.gargle.HOWL \
--to=raman@users.sourceforge.net \
/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://git.savannah.gnu.org/cgit/emacs.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).