Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Let's get effective!
Date: 14 Mar 1996 06:35:02 +0100	[thread overview]
Message-ID: <x6g2bc9tss.fsf@eyesore.no> (raw)
In-Reply-To: Steven L Baur's message of 12 Mar 1996 20:10:02 -0800

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

> I trust you are optimizing for reduced memory usage also?

You'd be wrong to trust me to do anything.  :-)

Anyways, I've now hacked up alloc.c to defvar all the interesting
alloc variables and I've hacked up elp.el to profile using these
variables to monitor for consing, stringsing, vectoring and so on.  It
even looks like it might be working!  

We'll see what comes of it.

I've done some slight calculation on what how much memory Gnus should
theoretically use for each article in a group.  The answer is:

(+ (* (+ 6 10 20) 8) 200 200)
  => 688 bytes

That means that Emacs should grow with half a meg when entering a 1000
article group the first time.  I think we can all agree that Emacs
grows quite a bit more.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


      parent reply	other threads:[~1996-03-14  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-13  3:12 Lars Magne Ingebrigtsen
1996-03-13  4:10 ` Steven L Baur
1996-03-13  5:08   ` d. hall
     [not found]     ` <yyaka0oordz.fsf@arls2006.fuentez.com>
1996-03-13 18:46       ` Steven L Baur
1996-03-13 20:11         ` Joe Hildebrand
1996-03-13 20:37           ` William Perry
1996-03-15 16:30           ` Timo Metzemakers
1996-03-15 19:41             ` Joe Hildebrand
1996-03-14  5:35     ` Lars Magne Ingebrigtsen
1996-03-14  5:35   ` Lars Magne Ingebrigtsen [this message]

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=x6g2bc9tss.fsf@eyesore.no \
    --to=larsi@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).