From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, deng@randomsample.de, mattiase@acm.org,
emacs-devel@gnu.org, gregory@heytings.org, larsi@gnus.org
Subject: Re: Timings for 'make check' with and without symbols with position
Date: Tue, 1 Mar 2022 19:59:10 +0000 [thread overview]
Message-ID: <Yh57Dm/jiJcEPTrn@ACM> (raw)
In-Reply-To: <83ilt0o5db.fsf@gnu.org>
Hello, Eli.
On Sun, Feb 27, 2022 at 14:34:24 +0200, Eli Zaretskii wrote:
> > Date: Sun, 27 Feb 2022 12:15:14 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: ofv@wanadoo.es, deng@randomsample.de, mattiase@acm.org, emacs-devel@gnu.org,
> > gregory@heytings.org, larsi@gnus.org
> > Char-tables seem to have something to do with it. The perf output for
> > mark_char_table increase from 2.98% to 3.79%. Adding the 12.6% factor
> > onto the 3.79% gives us 4.27%. That's a factor of ~1.5 increase.
> > I'm still slogging through the detailed output for mark_char_table,
> > which is not easy in the optimised build. I suspect that somehow,
> > somewhere, symbols with position have got themselves into a char-table,
> > and they take (a lot) longer to process than bare symbols (for which
> > mark_char_table is optimised). I've not yet managed to find such a
> > char-table though.
> We do have a few char-tables whose slots are symbols or include
> symbols. unicode-category-table is one, for example;
> composition-function-table is another.
I've instrumented mark_char_table to try and detect symbols with
position, but got no hits.
I similarly instrumented mark_vectorlike, but the only hits I got there
seemed to be when a compilation was in progress.
So elucidation eludes me, so far. I'll need to look at it in some other
fashion (suggestions welcome).
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2022-03-01 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 16:39 Timings for 'make check' with and without symbols with position Alan Mackenzie
2022-02-26 16:55 ` Eli Zaretskii
2022-02-27 12:15 ` Alan Mackenzie
2022-02-27 12:34 ` Eli Zaretskii
2022-03-01 19:59 ` Alan Mackenzie [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yh57Dm/jiJcEPTrn@ACM \
--to=acm@muc.de \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=ofv@wanadoo.es \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).