unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: slow find-file for network file systems and very deep	directories
Date: Tue, 16 Sep 2008 21:54:41 +0300	[thread overview]
Message-ID: <u8wtrq5u6.fsf@gnu.org> (raw)
In-Reply-To: <48CF2ECE.1050602@ggmail.com>

> From: AlFire <spamgrinder.trylater@ggmail.com>
> Date: Mon, 15 Sep 2008 20:58:06 -0700
> 
> Eli Zaretskii wrote:
> > 
> > Does it help to set w32-get-true-file-attributes to a nil value?
> > 
> > 
> 
> did not help - I tested it. and probably should since describe-variable says it is NTFS only:
> 
> 
> Documentation:
> Non-nil means determine accurate link count in `file-attributes'.
> Note that this option is only useful for files on NTFS volumes, where hard links
> are supported.  Moreover, it slows down `file-attributes' noticeably.

No, that's not what the doc string says: it says that the option is
_useful_ only on NTFS volumes, i.e. it will only get more accurate
file attributes on NTFS.  But it slows down Emacs on all types of
volumes, and networked volumes get generally hit the most.

> what else? could it be really considered a bug. from the original trace - I noted that Emacs is kind of looking for a source control related files like: .bzr\checkout\, _MTN, {arch}\, MCVS\ and walking thru the tree structure multiple times.

I don't see anything wrong with the trace, since RET in the minibuffer
actually tries to see if there are files in the directory that match
what you typed so far.

Can you compare the time it takes to visit the file when you type "C-x
C-f" with what happens when you type this instead:

   M-: (find-file "W:\dir1\dir2\dir3\dir4\dir5\dir6\dir7\dir8\dir9\dirA\dirB\dirC\file.c") RET

Also, do you happen to know if this was significantly faster in
previous Emacs versions?




  reply	other threads:[~2008-09-16 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  2:56 slow find-file for network file systems and very deep directories AlFire
2008-09-12  5:38 ` Drew Adams
2008-09-12  6:25 ` Eli Zaretskii
     [not found] ` <mailman.19095.1221200712.18990.help-gnu-emacs@gnu.org>
2008-09-13  2:25   ` AlFire
2008-09-13  8:14     ` Eli Zaretskii
     [not found]     ` <mailman.19168.1221293665.18990.help-gnu-emacs@gnu.org>
2008-09-16  3:58       ` AlFire
2008-09-16 18:54         ` Eli Zaretskii [this message]
     [not found]         ` <mailman.19372.1221591281.18990.help-gnu-emacs@gnu.org>
2008-09-19  1:19           ` AlFire
2008-09-19  9:01             ` Eli Zaretskii
     [not found]             ` <mailman.19537.1221814919.18990.help-gnu-emacs@gnu.org>
2008-09-23  3:34               ` AlFire

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=u8wtrq5u6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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.
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).