Eli Zaretskii <e...@gnu.org> writes: >> Based on =profiler-report=, the following function "chains" consume most of >> the >> CPU: >> - `font-lock-fontify-keywords-region' >> - tramp-sh-file-name-handler >> - tramp-sh-handle-file-truename >> - `tramp-wait-for-regexp' >> - tramp-sh-handle-file-exists-p >> - `tramp-wait-for-regexp' >> - tramp-sh-handle-file-directory-p >> - `tramp-wait-for-regexp' >> - tramp-sh-handle-file-attributes >> - `tramp-wait-for-regexp' >> >> As noted previously, disabling global-font-lock-mode helps. > > FWIW, I cannot reproduce this: I tried Dired on a remote host with > which I have connection that is quite slow, and saw neither high CPU > usage nor a significant delay in displaying a Dired buffer.
In my case, the directory in question had 22 symlinks. How many symlinks did you try with? -- Suhail
