From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 68249@debbugs.gnu.org
Subject: bug#68249: 30.0.50; Rmail summaries much slower
Date: Sun, 07 Jan 2024 09:27:21 +0200 [thread overview]
Message-ID: <835y05siw6.fsf@gnu.org> (raw)
In-Reply-To: <E1rMKp7-0003MD-1C@fencepost.gnu.org> (message from Richard Stallman on Sat, 06 Jan 2024 23:31:45 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: 68249@debbugs.gnu.org
> Date: Sat, 06 Jan 2024 23:31:45 -0500
>
> 1573 54% + command-execute
> 1098 38% Automatic GC
> 159 5% + timer-event-handler
> 25 0% + ...
> 19 0% redisplay_internal (C function)
> 8 0% + rmail-summary-rmail-update
>
> I am not sure what that implies, since nothing in a loop
> to check messages appears in it.
You didn't expand the profile. All those lines which have a "+"
before the function's name are "folded", and you can "unfold" them by
going to the line and pressing RET. "C-u RET" will unfold _all_ such
folded lines, and you will see the detailed profile of
command-execute, which I think where the problem happens, and where
you will find the loop that checks messages (or a function that runs
such a loop).
> Should I try this in the previous version for comparison?
That could help, yes. But before that, I think a fully expanded
("unfolded") profile of the current version is needed.
It is also strange that GC takes such a large proportion of time. It
is possible that the slowdown is because some subroutine makes much
more garbage than the previous implementation did.
next prev parent reply other threads:[~2024-01-07 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 4:23 bug#68249: 30.0.50; Rmail summaries much slower Richard Stallman
2024-01-05 8:55 ` Eli Zaretskii
2024-01-07 4:31 ` Richard Stallman
2024-01-07 7:27 ` Eli Zaretskii [this message]
2024-01-24 4:16 ` Richard Stallman
2024-01-24 10:03 ` Stefan Kangas
2024-01-24 12:30 ` Eli Zaretskii
2024-01-27 3:36 ` Richard Stallman
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=835y05siw6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68249@debbugs.gnu.org \
--cc=rms@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 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).