Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: any tips for how to tune Gnus/emacs for low memory usage?
Date: Sun, 25 Nov 2001 20:55:28 +0100	[thread overview]
Message-ID: <87snb2tyku.fsf@bang.priv.no> (raw)

Platform: GNU Emacs 20.7.2, Oort Gnus v0.04 (CVS update from october 6)
          using the nnimap and nntp backends, with Gnus agent,
          Intel P133, debian woody linux w/the 2.2.19 kernel

I'm running Gnus inside of GNU emacs under linux and XFree86, on what
today is a small machine: P133 with 24 MB of RAM (top reports 22724k
total.  Presumably the rest of the memory is taken by the kernel).

My problem is that things start to get slow when the size of the emacs
process approaches the size of the physical memory, and the system
starts paging at the drop of a hat.  What drives memory consumption up
to this level is in my case, opening the newsgroup no.alt.motorsykler.

In this group I have ticked some old articles, and since I'm using the
agent they never expire.  The group has a lot of traffic, which means
that Gnus have fill in all the empty space between the article numbers
when opening the group.

In addition I do a lot of scoring in this group.  I guess the followup
scoring of some persons really add to the cost.  I also do adaptive
scoring based on reading, and deleting of articles.

Is there anything I can try to keep the size of the Emacs process
down?  Stay completely away from groups with sparse article numbers?
Stay away from adaptive/followup scoring?

Or are there some variables I could try tuning to keep the memory
usage down?


- Steinar



             reply	other threads:[~2001-11-25 19:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25 19:55 Steinar Bang [this message]
2001-11-26  4:21 ` Stainless Steel Rat
2001-11-26 21:57   ` Steinar Bang
2001-11-26 22:45     ` Karl Kleinpaste
2001-11-27  3:29     ` Stainless Steel Rat
2001-11-27 12:38     ` Daniel Pittman
2001-11-27 14:11     ` news
2001-11-27 14:27       ` luis fernandes
2001-11-27 16:24         ` news
2001-11-27 16:56           ` Kai Großjohann
2001-11-27 20:28           ` news
2001-11-27 19:13       ` Stainless Steel Rat
2001-11-27 19:30         ` luis fernandes
2001-11-27 19:37           ` Robin S. Socha
2001-11-27 20:06             ` luis fernandes
2001-11-27 21:50               ` news
2001-11-28 23:02               ` Steinar Bang
2001-11-29  8:33                 ` Kai Großjohann
2001-11-29 14:30                   ` news
2001-12-01  9:59                   ` Steinar Bang
2001-11-27 19:40         ` Paul Jarc
2001-11-30 23:19           ` Kevin Ryde
2001-11-30 13:51         ` news
2001-11-30 16:58           ` Stainless Steel Rat

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=87snb2tyku.fsf@bang.priv.no \
    --to=sb@dod.no \
    /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).