From: Michael Heerdegen <michael_heerdegen@web.de>
To: info-gnus-english@gnu.org
Subject: Re: slow saving of scores when leaving a virtual (nnml+) group
Date: Fri, 14 Jul 2023 01:56:35 +0200 [thread overview]
Message-ID: <87351re570.fsf@web.de> (raw)
In-Reply-To: <878rbkf1pm.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> 832,940,181 99% - command-execute
> 805,535,710 96% - funcall-interactively
> 540,874,166 64% - gnus-summary-exit
> 537,712,423 64% - gnus-score-save
> 536,634,533 64% - gnus-pp
> [...]
>
> It could be that I am misinterpreting those profiler results.
I think so, yes. These numbers cannot be interpreted directly as used
memory. It's more like "time spent inside the function, measured
memory-usage wise.
> I tried this as well and also get results immediately.
Hmm. Ok. We could try with M-x trace-function pp-to-string RET
directly before `gnus-summary-exit'. A popup buffer should appear, and
it would be helpful if you could again post the output (with any private
data obfuscated; we are interested in the argument(s) of the function
call(s)). But before that please M-x untrace-all RET.
> > Have you tried to change the value of `pp-default-function' btw?
>
> No, it's set to pp-fill.
Are things significantly faster when setting this to pp-28?
Thx,
Michael.
next prev parent reply other threads:[~2023-07-13 23:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 11:45 Eric S Fraga
2023-07-06 15:43 ` Eric Abrahamsen
2023-07-07 7:05 ` Eric S Fraga
2023-07-07 15:41 ` Eric Abrahamsen
2023-07-08 8:52 ` Eric S Fraga
2023-07-08 1:22 ` Michael Heerdegen
2023-07-08 8:51 ` Eric S Fraga
2023-07-09 5:23 ` Michael Heerdegen
2023-07-10 15:41 ` Eric S Fraga
2023-07-11 2:56 ` Michael Heerdegen
2023-07-11 9:18 ` Eric S Fraga
2023-07-12 0:48 ` Michael Heerdegen
2023-07-12 10:08 ` Eric S Fraga
2023-07-13 0:18 ` Michael Heerdegen
2023-07-13 12:14 ` Eric S Fraga
2023-07-13 23:56 ` Michael Heerdegen [this message]
2023-07-14 11:05 ` Eric S Fraga
2023-07-16 2:55 ` Michael Heerdegen
2023-07-17 7:32 ` Eric S Fraga
2023-07-18 6:16 ` Michael Heerdegen
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=87351re570.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).