Gnus development mailing list
 help / color / mirror / Atom feed
From: Anders Melchiorsen <postmaster@and.nospam.kampsax.k-net.dk>
Subject: Solved: Re: Slow and big Gnus 5.8.x
Date: 04 Mar 2000 23:32:05 +0100	[thread overview]
Message-ID: <m3vh32xt7e.fsf_-_@k0817.kampsax.dtu.dk> (raw)
In-Reply-To: Karl Kleinpaste's message of "04 Mar 2000 10:11:22 -0500"

Karl Kleinpaste <karl@justresearch.com> wrote:

> Anders Melchiorsen <postmaster@and.nospam.kampsax.k-net.dk> writes:
> > Especially when I enter a group, Gnus is slower in generating the
> > summary and it is virtually impossible for me to enter groups with,
> > say, 2000 articles (since Emacs grows to an image size that my 64MB of
> > RAM simply cannot handle).
> 
> I don't know why you'd have that much trouble.  My normal Gnus

Shame on me.

While I did produce some depressing timings to back up my case, I also
found out that I was in fact using an uncompiled Gnus. Compiling it
did improve both memory usage and speed considerably. I guess I should
have done that two months ago...

So, the lesson learned was that one thing to remember when installing
a new Gnus is to correct your paths :-/.

Thanks for your help nevertheless.

> On the other hand, I notice you're using a recent XEmacs 21.  Is it
> perhaps compiled with debugging enabled?  You will see some fairly
> drastic speed improvement if you ./configure --error-checking=none
> --debug=no.

I am using the RPM from www.xemacs.org - I suppose they are properly
built?

-- 
Regards, Anders
(address is valid)



  reply	other threads:[~2000-03-04 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-04 14:03 Anders Melchiorsen
2000-03-04 15:11 ` Karl Kleinpaste
2000-03-04 22:32   ` Anders Melchiorsen [this message]
2000-03-05 13:30     ` Solved: " Anders Melchiorsen
2000-03-04 16:44 ` Kai Großjohann

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=m3vh32xt7e.fsf_-_@k0817.kampsax.dtu.dk \
    --to=postmaster@and.nospam.kampsax.k-net.dk \
    /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).