|
From: | Dmitry Gutov |
Subject: | Re: Reliable after-change-functions (via: Using incremental parsing in Emacs) |
Date: | Wed, 1 Apr 2020 18:22:00 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
On 01.04.2020 16:52, Alan Mackenzie wrote:
This doesn't seem to affect starting up performance that badly. On my machine (a 3 yo AMD Ryzen) visiting xdisp.c (including the fontification of the first screenful of comments) is taking 0.18s.
Interesting. How do you measure it exactly? Do you kill the buffer between tries?
I have a fast Intel CPU that is barely 2 years old (i9-8950HK), system-configuration-options is "--with-x-toolkit=gtk3 'CFLAGS=-Og -g3'", the build is from emacs-27 branch, recent revision.
With 'emacs -Q' it's a little faster, but still (benchmark 1 '(progn (find-file "src/xdisp.c"))) prints out Elapsed time: 0.968598s (0.144805s in 8 GCs)
[Prev in Thread] | Current Thread | [Next in Thread] |