|
From: | Dmitry Gutov |
Subject: | bug#56682: Fix the long lines font locking related slowdowns |
Date: | Fri, 5 Aug 2022 20:32:32 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 |
On 05.08.2022 18:33, Eli Zaretskii wrote:
Date: Fri, 5 Aug 2022 17:41:51 +0300 Cc: monnier@iro.umontreal.ca, 56682@debbugs.gnu.org, gregory@heytings.org From: Dmitry Gutov <dgutov@yandex.ru>
I think I have
demonstrated that the remaining slowdown can be caused purely by the length of the buffer and how long 'parse-partial-sexp' takes to parse it.No, you haven't demonstrated that.Apply the patch for xdisp.c that I have sent previously (it will be at the end of this email too) and recompile Emacs. Now try two different scenarios. 1,2a and 1,2b. 1. Visit dictionary.json. It will ask you whether to open such big file literally, but after you answer 'y', it will display the beginning of the file quickly. 2a) Evaluate (benchmark 1 '(save-excursion (parse-partial-sexp 1 (point-max)))), note the reported delay. Kill and re-visit the file. 1. (same as before) 2b) Press M->, note the delay you see. The delays in scenarios 1,2a and 1,2b should be ~the same. They are so in my testing. Or try this scenario: 1,2a,2b. Step 2b should work instantly here.How is (parse-partial-sexp 1 (point-max)) related to the issue at hand?
I said: >>>> I think I have >>>> demonstrated that the remaining slowdown can be caused purely by the >>>> length of the buffer and how long 'parse-partial-sexp' takes to parse >>>> it. You said: >>> No, you haven't demonstrated that. ...and now you are asking why we are talking about parse-partial-sexp?
[Prev in Thread] | Current Thread | [Next in Thread] |