From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: any tips for how to tune Gnus/emacs for low memory usage?
Date: Tue, 27 Nov 2001 23:38:04 +1100 [thread overview]
Message-ID: <87wv0c9yoj.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <87pu65xkj0.fsf@bang.priv.no> (Steinar Bang's message of "Mon, 26 Nov 2001 22:57:39 +0100")
On Mon, 26 Nov 2001, Steinar Bang wrote:
>>>>>> Stainless Steel Rat <ratinox@peorth.gweep.net>:
>
>> You have barely enough memory for the X server, and not nearly
>> enough for X and Emacs.
>
> Running KDE or Gnome is out, but the X server itself isn't all that
> much of a hog. And I'm using icewm as the WM, which uses only around
> 800k.
Quite. X, contrary to rumors, is rather light-weight. I happily ran it
on my P-133 with 24MB of ram for an awful while. :)
> 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.
>
> The two big culprits, according to top, are emacs/Gnus (after visiting
> one of the problem groups), and opera.
The best I ever found for keeping the size of the Emacs process that was
running stuff down was to keep Gnus distinct from my standard Emacs[1],
to ensure that W3 was *not* available under Gnus, and to make sure I
never kept ticked articles lying around for long.
Oh, and I had fairly small groups at the time, though that doesn't seem
to have made that much difference...
> I'll try out galeon when it moves out of debian unstable, and into
> testing.
I doubt that you will be happy; this is a very light session:
3633 daniel 9 0 45040 41M 18224 S 0 0.0 14.5 2:59 galeon-bin
3638 daniel 9 0 45040 41M 18224 S 0 0.0 14.5 0:00 galeon-bin
3639 daniel 9 0 45040 41M 18224 S 0 0.0 14.5 0:04 galeon-bin
3640 daniel 9 0 45040 41M 18224 S 0 0.0 14.5 0:00 galeon-bin
4788 daniel 9 0 45040 41M 18224 S 0 0.0 14.5 0:00 galeon-bin
6786 daniel 9 0 45040 41M 18224 S 0 0.0 14.5 0:00 galeon-bin
That's not exactly a light-weight browser, and it bloats relatively fast.
> But I don't really have a replacement candidate for Gnus.
I never met anything better. :0
> I'll also try out the 2.4-series to see if the VM is more efficient.
It's a heavier footprint than 2.2 but 2.4.16-pre1 and close to that are
fairly good. They swap sooner, feel decent interactively and don't have
too many harsh edges.
Daniel
Footnotes:
[1] I did this briefly, but stopped for the lack of integration.
--
There is no female mind. The brain is not an organ of sex.
As well to speak of a female liver.
-- Charlette Perkins Gilman, _Women and Economics_
next prev parent reply other threads:[~2001-11-27 12:38 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
2001-11-27 3:29 ` Stainless Steel Rat
2001-11-27 12:38 ` Daniel Pittman [this message]
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=87wv0c9yoj.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).