From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: info-gnus-english@gnu.org
Subject: Re: slow saving of scores when leaving a virtual (nnml+) group
Date: Fri, 14 Jul 2023 12:05:36 +0100 [thread overview]
Message-ID: <87wmz2ah33.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87351re570.fsf@web.de>
On Friday, 14 Jul 2023 at 01:56, Michael Heerdegen wrote:
> 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.
Ah, okay. Total misunderstanding on my part!
> 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.
The trace output is difficult to obfuscate so I won't include it here
but what it shows is that the function is passed the full contents of
the adaptive scoring file, not the static score file.
> Are things significantly faster when setting this to pp-28?
Very much so! Group exists almost immediately, back to what I used to
see. With pp-28, I'm happy! Problem solved. :-)
Thank you,
eric
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-07-10) on Debian 12.0
next prev parent reply other threads:[~2023-07-14 11:06 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
2023-07-14 11:05 ` Eric S Fraga [this message]
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=87wmz2ah33.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).