Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: strange memory usage for nntp groups
Date: Thu, 28 Dec 2017 18:51:15 +0000	[thread overview]
Message-ID: <87k1x6hejg.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87lghmsoa7.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

On Thursday, 28 Dec 2017 at 18:25, Eric S Fraga wrote:
> On Thursday, 28 Dec 2017 at 04:04, Emanuel Berg wrote:
>
> [...]
>
>> From what I can understand from the manual
>> entry, yanked last in this posts, the overview
>> files are generated by Gnus only for nnml; for
>> NNTP, the server makes them, so I suppose
>> additions are communicated and
>> appended locally.
>>
>> If so, deleting a file will help but eventually
>> it will grow back to size.
>
> Well, I deleted the .overview file and I was able to enter the group and
> read the posts in it.  Memory usage went up only marginally.  Simple
> enough to make a cron script or equivalent that deletes .overview files
> that get too large, I guess.

I take it back.  Deleting the .overview file is not a good idea.  It
makes it impossible to retrieve any old articles at all.  I've had to
recreate the group from the server to get at any old articles.

Can anybody suggest how I can read large newsgroups on systems with
small memory?  I would have thought that gnus should be able to do
this.  Does it need to keep the whole set of headers in memory?  I'm
happy to pay the price of network access in lieu of memory overload...

Thanks,
eric

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2017-12-28 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-27 21:06 Eric S Fraga
2017-12-27 23:24 ` Emanuel Berg
2017-12-27 23:55   ` Eric S Fraga
2017-12-28  3:04     ` Emanuel Berg
2017-12-28 18:25       ` Eric S Fraga
2017-12-28 18:51         ` Eric S Fraga [this message]
2017-12-28 19:03           ` Emanuel Berg
2017-12-28 10:31 ` Steinar Bang
2017-12-28 18:30   ` Eric S Fraga

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=87k1x6hejg.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=ding@gnus.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).