From: Shuguang Sun <shuguang@gmail.com>
To: 29846@debbugs.gnu.org
Subject: bug#29846: scroll and fontify takes longer time for file in slow network
Date: Mon, 25 Dec 2017 14:03:43 +0800 [thread overview]
Message-ID: <CACspjXdWGoGQUK2OXPC16ZEO2_TGvzMYmt6sszR2auJXupUK0A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
Hi,
Windows 7, GNU Emacs 27.0.50 (build 1, x86_64-w64-mingw32) of 2017-12-09.
Issue:
I have remote dirver (//server/path) mapped to my windows system (samba?).
The network is slow, and it takes some time to open the file. However,
after I have the file opened and scroll down, it takes a long time to
scroll to the next screen. It gets worse if the jit-lock-debug-mode is on.
After that if I try to scroll back to those has been fontified, it get
fluent as expected.
If I open the same file in a local driver (speed is higher than the network
definitely), the scroll is very fluent.
If I open a txt file (fundmental-mode, not fontification) in the same
remote directory, the scroll actions are fluent as well.
Per my understanding, all actions should be done in memory when a file has
been read into buffer, except backup, autosave, etc. The response should
not depents on where the file located phically.
How to repeat it:
1. Find a slow transfer rate network (sorry, it may be hard)
2. Prepare a long c file, 3-4 screens.
3. take font-lock-mode on (jit-font-mode)
4. Open the c file and scroll down, scroll down, scroll down...
5. scroll up, scroll up, scroll up
I have tried profiler. It indicates, the jit-font and redisplay take
majority of the cpu time.
1. open the c file
2. profiler-start
3. scroll down, scroll down, scroll down...
4. profiler-report
Best Regards,
Shuguang Sun
[-- Attachment #2: Type: text/html, Size: 1793 bytes --]
next reply other threads:[~2017-12-25 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 6:03 Shuguang Sun [this message]
2017-12-25 9:47 ` bug#29846: scroll and fontify takes longer time for file in slow network Shuguang Sun
2017-12-25 12:28 ` Eli Zaretskii
2017-12-25 14:41 ` Shuguang Sun
2017-12-25 16:48 ` Eli Zaretskii
2017-12-26 1:04 ` Shuguang Sun
2017-12-27 20:49 ` Stefan Monnier
2017-12-28 16:21 ` Eli Zaretskii
2017-12-28 19:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACspjXdWGoGQUK2OXPC16ZEO2_TGvzMYmt6sszR2auJXupUK0A@mail.gmail.com \
--to=shuguang@gmail.com \
--cc=29846@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.