From: Eli Zaretskii <eliz@gnu.org>
To: Mathias Dahl <mathias.dahl@gmail.com>
Cc: 5833@debbugs.gnu.org
Subject: bug#5833: 23.1.94; Opening files on network shares on w32 is slow
Date: Tue, 06 Apr 2010 00:58:39 +0300 [thread overview]
Message-ID: <83mxxhy31s.fsf@gnu.org> (raw)
In-Reply-To: <r2n7dbe73ed1004051115ldfed152u1395d81103aefa56@mail.gmail.com>
> From: Mathias Dahl <mathias.dahl@gmail.com>
> Date: Mon, 5 Apr 2010 20:15:47 +0200
> Cc: 5833@debbugs.gnu.org
>
> > Btw, is "C-x C-f" faster than Dired, by any chance?
>
> No, at least not enough to be measured with a stop watch.
>
> > Can you tell if setting the following variables has any effect?
> >
> > (setq vc-handled-backends nil)
>
> From having taken close to 8 seconds (tried repeatedly), after this
> change it takes almost 6, so 2 s better. Still a long time, but
> better.
>
> > (setq locate-dominating-stop-dir-regexp "")
>
> That maybe shaves off half a second. Again, hard to done any
> scientific tests using a physical stop watch.
That's strange: I thought they would slash much more.
How about insert-file-contents and insert-file-contents-literally --
can you time those?
Another idea is to use elp.el to profile the various functions called
by find-file. At least for the Lisp level, we will see where's the
bottleneck, and that might give some ideas.
next prev parent reply other threads:[~2010-04-05 21:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 21:16 bug#5833: 23.1.94; Opening files on network shares on w32 is slow Mathias Dahl
2010-04-04 6:00 ` Eli Zaretskii
2010-04-05 11:35 ` Mathias Dahl
2010-04-05 12:33 ` Eli Zaretskii
2010-04-05 18:15 ` Mathias Dahl
2010-04-05 20:15 ` Stefan Monnier
2010-04-05 21:03 ` Mathias Dahl
2010-04-06 0:12 ` Jason Rumney
2010-04-06 0:46 ` Stefan Monnier
2010-04-05 21:58 ` Eli Zaretskii [this message]
2010-04-06 7:12 ` Mathias Dahl
2010-04-06 8:15 ` martin rudalics
2010-04-06 18:16 ` Eli Zaretskii
2010-04-07 2:53 ` Eli Zaretskii
2010-04-07 21:00 ` Mathias Dahl
2019-08-08 3:30 ` Stefan Kangas
2019-08-08 13:21 ` Eli Zaretskii
2019-08-23 17:36 ` Stefan Kangas
2019-08-23 19:27 ` Eli Zaretskii
2019-08-24 8:46 ` Mathias Dahl
2019-08-24 10:13 ` Eli Zaretskii
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=83mxxhy31s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5833@debbugs.gnu.org \
--cc=mathias.dahl@gmail.com \
/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).