Gnus development mailing list
 help / color / mirror / Atom feed
From: hardaker@ece.ucdavis.edu (Wes Hardaker)
Cc: ding@ifi.uio.no
Subject: Re: Gnus Memory usage
Date: 23 Feb 1996 09:24:45 -0800	[thread overview]
Message-ID: <sdohqqlztu.fsf@teal.ece.ucdavis.edu> (raw)
In-Reply-To: Steven L Baur's message of 22 Feb 1996 17:39:59 -0800

>>>>> "Steven" == Steven L Baur <steve@miranova.com> writes:

    Steven> Why kill and restart Gnus several times in the same XEmacs
    Steven> session?  The amount of time lost waiting for garbage
    Steven> collection as the size increases easily surpasses the
    Steven> amount of time it takes to restart the program from
    Steven> scratch.  It doesn't appear to hurt anything (if you have
    Steven> the memory available) to just leave Gnus always running.
    Steven> Disconnection is automatic, and reconnection is painless.

Well, this is what I've started doing more lately.  Originally, I just
did it automatically thinking I wouldn't be reading news later.  It
was then that I noticed things got even worse during the second read.
At the time, I didn't read any mail inside gnus, so it was unusual to
read news twice in one day.  Again, I haven't checked this out in a
while so it may not happen anymore.

However, if it does shrink XEmacs to quit gnus, that alone might be
enough of a reason (though I think we've proven it doesn't shrink by
much).  When I'm actually trying to get some work done, my HP 715/80
with 96 megs of memory swaps constantly while running Mentor (a
bloated EE CAD program).  I often quit XEmacs all together before
starting Mentor.

blah blah blah
Wes



  reply	other threads:[~1996-02-23 17:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-21  2:26 September Gnus 0.40 is released Lars Magne Ingebrigtsen
1996-02-21  3:20 ` Steven L Baur
1996-02-21 11:06   ` Per Abrahamsen
1996-02-21 19:00     ` Steven L Baur
1996-02-21 21:50       ` Andy Eskilsson
1996-02-22  1:12       ` Lars Magne Ingebrigtsen
1996-02-22  8:22         ` d. hall
1996-02-22 18:03           ` Lars Magne Ingebrigtsen
1996-02-22 20:49             ` Steven L Baur
1996-02-21  4:14 ` d. hall
1996-02-21  6:55   ` Gnus Memory usage Steven L Baur
1996-02-21 16:38     ` Wes Hardaker
1996-02-22  1:12       ` Lars Magne Ingebrigtsen
1996-02-22 23:19         ` Wes Hardaker
1996-02-22 23:50           ` Lars Magne Ingebrigtsen
1996-02-23 17:19             ` Wes Hardaker
1996-02-24  7:44               ` Lars Magne Ingebrigtsen
1996-02-24  9:26                 ` d. hall
1996-02-26 18:01                   ` Stephen Peters
1996-02-26 18:12                 ` Wes Hardaker
1996-02-23  1:39           ` Steven L Baur
1996-02-23 17:24             ` Wes Hardaker [this message]
1996-02-23 21:57             ` Mark Denovich
1996-02-24  7:44               ` Lars Magne Ingebrigtsen
1996-02-24 22:08                 ` dynamic ip (Re: Gnus Memory usage) Felix Lee
1996-02-24 22:33                   ` Lars Magne Ingebrigtsen
1996-02-25  0:35                     ` Felix Lee
1996-02-21 17:59     ` Gnus Memory usage Mark Borges

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=sdohqqlztu.fsf@teal.ece.ucdavis.edu \
    --to=hardaker@ece.ucdavis.edu \
    --cc=ding@ifi.uio.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).