Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: ding@gnus.org
Subject: Re: strange memory usage for nntp groups
Date: Thu, 28 Dec 2017 00:24:27 +0100	[thread overview]
Message-ID: <86k1x7n49g.fsf@zoho.com> (raw)
In-Reply-To: <878tdnhocx.fsf@ucl.ac.uk>

Eric S Fraga wrote:

> Is there some variable that I may be setting
> that affects memory use so dramatically?
> Or is there some variable I should set to
> avoid this problem? I have set
> gnus.thread.refer.limit to 0 but have done no
> other tests.

Could this be the same thing I have reported
a couple of times? I.e. the huge .overview
files? E.g., my gmane.emacs.help ditto isn't
that big at the moment - only 36M!

    $ find ./ -name .overview -exec ls -lh {} \;

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2017-12-27 23:24 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 [this message]
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
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=86k1x7n49g.fsf@zoho.com \
    --to=moasen@zoho.com \
    --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).