From: David Engster <deng@randomsample.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Anand Tamariya <atamariya@gmail.com>
Subject: Re: Semantic font-lock for Java
Date: Fri, 24 Jan 2020 18:00:02 +0100 [thread overview]
Message-ID: <87tv4kyelp.fsf@randomsample> (raw)
In-Reply-To: <83k15grflg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 24 Jan 2020 18:20:27 +0200")
>> From: Anand Tamariya <atamariya@gmail.com>
>> Date: Fri, 24 Jan 2020 21:45:55 +0530
>> Cc: emacs-devel@gnu.org
>
>>
>> > * Off GCs: 0 Elapsed time: 0.840946 seconds
>> > * Custom GCs: 0 Elapsed time: 1.172106 seconds
>> > * Builin GCs: 1 Elapsed time: 0.991606 seconds
>>
>> I'm not sure I understand these results. What does each line
>> represent? Did you run the same benchmark with the default font-lock
>> and with your modifications, and if so, which of these lines shows
>> results for what variant of font-lock?
>>
>> Off - Refers to when font-lock is disabled
>> Custom - Refers to when my "extract" function is doing the fontification
>> Builtin - Refers to jit-lock mode as that's the default for font-lock mode
>
> So we are talking about a 17% slow-down? Not bad.
Yes, but to be fair, this does not include the initial parsing by
Semantic/Wisent/Bovine. This is usually done for the whole buffer when
Emacs is idle, and not during scrolling.
-David
next prev parent reply other threads:[~2020-01-24 17:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 11:39 Semantic font-lock for Java Anand Tamariya
2020-01-21 15:41 ` Eli Zaretskii
2020-01-21 15:48 ` Eli Zaretskii
2020-01-22 5:13 ` Anand Tamariya
2020-01-22 17:25 ` Eli Zaretskii
2020-01-23 5:36 ` Anand Tamariya
2020-01-24 7:40 ` Eli Zaretskii
2020-01-24 16:15 ` Anand Tamariya
2020-01-24 16:20 ` Eli Zaretskii
2020-01-24 17:00 ` David Engster [this message]
2020-01-24 19:59 ` Eli Zaretskii
2020-01-24 20:38 ` David Engster
2020-01-28 15:50 ` Anand Tamariya
2020-01-28 17:21 ` David Engster
2020-01-28 17:50 ` Eli Zaretskii
2020-01-29 5:14 ` Anand Tamariya
2020-02-03 3:24 ` Eric Ludlam
2020-01-28 19:43 ` Alan Mackenzie
2020-01-29 5:44 ` Anand Tamariya
2020-01-22 5:52 ` Anand Tamariya
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=87tv4kyelp.fsf@randomsample \
--to=deng@randomsample.de \
--cc=atamariya@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.