Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
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: Sat, 08 Jul 2023 09:51:26 +0100	[thread overview]
Message-ID: <87h6qepz01.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87o7kn9oz7.fsf@web.de>

On Saturday,  8 Jul 2023 at 03:22, Michael Heerdegen wrote:
> And - is it worth the time to pretty print this data at all?

This is what I was wondering.  The pretty printing could be saved for
when somebody wishes to edit the scores, at which point a little delay
is not intrusive (or as intrusive).  Most of the time, I just want the
scores updated quickly so I can go on to the next group.

What puzzles me is the very large amount of memory use.  My scores file
is 334 kB in size.  Why does this require half a GB of memory to
process?

-- 
Eric S Fraga via gnus (Emacs 30.0.50 2023-07-07) on Debian 12.0



  reply	other threads:[~2023-07-08  8:52 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 [this message]
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
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=87h6qepz01.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).