From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: any tips for how to tune Gnus/emacs for low memory usage?
Date: Mon, 26 Nov 2001 17:45:16 -0500 [thread overview]
Message-ID: <vxkbshpjgn7.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <87pu65xkj0.fsf@bang.priv.no> (Steinar Bang's message of "Mon, 26 Nov 2001 22:57:39 +0100")
Steinar Bang <sb@dod.no> writes:
> No problem at all running X and emacs without swapping... until I've
> used Gnus to visit one of the newsgroups that makes the emacs process
> size ballon.
You might check on your settings of things like gnus-fetch-old-headers
and gnus-build-sparse-threads. Using apropos (I have XEmacs with
hyper-apropos) to look at all the gnus.*header and gnus.*thread
possibilities is probably a good idea.
> In any case it is a matter of pride to make linux run faster, and work
> better, than Win95 did on the same machine. Adding memory would be
> cheating.
:-)
My poor old 486dx4/100 laptop has only 20M, and I've nearly given up
on X entirely. Without ever using anything so complex as Gnus, it
swaps merely by moving the mouse between xterms and XEmacs.
next prev parent reply other threads:[~2001-11-26 22:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 19:55 Steinar Bang
2001-11-26 4:21 ` Stainless Steel Rat
2001-11-26 21:57 ` Steinar Bang
2001-11-26 22:45 ` Karl Kleinpaste [this message]
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=vxkbshpjgn7.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).