|
From: | Jason Rumney |
Subject: | bug#5833: 23.1.94; Opening files on network shares on w32 is slow |
Date: | Tue, 06 Apr 2010 08:12:22 +0800 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 |
On 06/04/2010 04:15, Stefan Monnier wrote:
(setq locate-dominating-stop-dir-regexp "")That maybe shaves off half a second.Hmm... odd. That seemed like a pretty good guess (locate-dominating-file tends to suffer from such performance problems in some cases, and vc-handled-backends is one user of this function, and dir-locals is another, so setting locate-dominating-stop-dir-regexp should really kill it off).
I think it odd that it shaved time off rather than made things much worse. One of the reasons for this variable is that when Windows tries to locate all the siblings of //machine, and in some cases //machine/share (where the user only has access to some shares), the process takes a long time. Perhaps the original value is incorrect?
[Prev in Thread] | Current Thread | [Next in Thread] |