From: Russ Allbery <rra@stanford.edu>
Subject: Re: is it faster? :)
Date: 21 Jul 1999 02:45:44 -0700 [thread overview]
Message-ID: <yl1ze249pz.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Maciej Matysiak's message of "21 Jul 1999 11:13:56 +0200"
Maciej Matysiak <phoner@blah.pl> writes:
> or can it be just because i restarted xemacs after 32 days uptime and it
> doesn't take so much memory and stuff on my poor box (p120/64mb)?
I generally find that emacs's memory footprint continually increases until
I restart it (albeit slowly), and that it starts getting noticeably slower
as the memory footprint gets larger, even if the system isn't swapping.
I usually exit out and restart every few days because of this. I don't
think it's necessarily a leak; it's just that over that period of time I
end up doing something or other that uses a whole bunch of memory.
--
Russ Allbery (rra@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~1999-07-21 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-21 9:13 Maciej Matysiak
1999-07-21 9:45 ` Russ Allbery [this message]
1999-08-27 21:17 ` Lars Magne Ingebrigtsen
1999-07-22 22:06 ` Anil B. Somayaji
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=yl1ze249pz.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).