From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 51523@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org
Subject: bug#51523: 29.0.50; gnus-mime-view-part-externally very slow
Date: Wed, 03 Nov 2021 14:56:47 -0400 [thread overview]
Message-ID: <jwv35oddqjd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <11d5fecb44bcf5508ef3@heytings.org> (Gregory Heytings's message of "Wed, 03 Nov 2021 15:20:08 +0000")
>>> - (sym (concat (symbol-name tag) "@" file))
>>> + (sym (concat (symbol-name tag) "@"
>>> + (if (file-name-absolute-p file)
>>> + file
>>> + (expand-file-name file))))
>> (cons tag (if (file-name-absolute-p file) file (expand-file-name file)))
>> is more efficient.
> I don't see a performance impact in my tests, but I'll trust the master.
It's likely lost in the noise, indeed, but `cons` just allocates
a single 2-word object, whereas your concat will allocate a Lisp_String
object (4-word object) plus the actual byte array (of N+M+1 bytes).
[ And if you're unlucky and one of the strings has text-properties
applied to it, then you get a fair bit more since the interval tree
then needs to be copied (and merged if both strings have
properties). ]
It also gives you cleaner behavior, since it avoids the possibility of
freak collisions when tag or file contains `@`. IOW, it should be the
natural choice.
Stefan
next prev parent reply other threads:[~2021-11-03 18:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 4:11 bug#51523: 29.0.50; gnus-mime-view-part-externally very slow Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-31 15:27 ` Lars Ingebrigtsen
2021-10-31 21:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-31 23:41 ` Gregory Heytings
2021-11-01 0:01 ` Lars Ingebrigtsen
2021-11-01 0:11 ` Gregory Heytings
2021-11-01 0:15 ` Lars Ingebrigtsen
2021-11-01 2:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-01 13:38 ` Lars Ingebrigtsen
2021-11-01 0:17 ` Gregory Heytings
2021-11-01 0:21 ` Lars Ingebrigtsen
2021-11-01 0:55 ` Gregory Heytings
2021-11-01 1:24 ` Gregory Heytings
2021-11-01 1:26 ` Gregory Heytings
[not found] ` <6abcac838bb94542451d@heytings.org>
2021-11-01 9:28 ` Gregory Heytings
[not found] ` <6abcac838bb83b0904d7@heytings.org>
[not found] ` <6abcac838bad7cded4c5@heytings.org>
2021-11-01 12:26 ` Gregory Heytings
2021-11-01 13:52 ` Lars Ingebrigtsen
2021-11-01 15:00 ` Eli Zaretskii
2021-11-01 15:20 ` Gregory Heytings
2021-11-01 15:23 ` Lars Ingebrigtsen
2021-11-01 16:46 ` Eli Zaretskii
2021-11-01 16:59 ` Lars Ingebrigtsen
2021-11-01 17:03 ` Eli Zaretskii
2021-11-01 17:15 ` Eli Zaretskii
2021-11-01 17:19 ` Lars Ingebrigtsen
2021-11-01 17:21 ` Eli Zaretskii
2021-11-01 17:23 ` Lars Ingebrigtsen
2021-11-01 17:28 ` Eli Zaretskii
2021-11-01 17:34 ` Lars Ingebrigtsen
2021-11-01 18:17 ` Eli Zaretskii
2021-11-01 21:14 ` Gregory Heytings
2021-11-02 14:50 ` Lars Ingebrigtsen
2021-11-02 15:12 ` Eli Zaretskii
2021-11-03 10:45 ` Gregory Heytings
2021-11-03 12:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 12:57 ` Gregory Heytings
2021-11-03 13:17 ` Eli Zaretskii
2021-11-03 13:27 ` Gregory Heytings
2021-11-03 13:53 ` Eli Zaretskii
2021-11-03 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 14:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 15:20 ` Gregory Heytings
2021-11-03 18:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-03 13:06 ` Eli Zaretskii
2021-11-01 0:04 ` Lars Ingebrigtsen
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=jwv35oddqjd.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=51523@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).