-----BEGIN PGP SIGNED MESSAGE-----

ð thus on Wed, 21 Feb 1996 15:06:41 -0800, Steven virtually scripted...

Steven> Memory leaks should be fixed where possible.  Memory intensive
Steven> features should be identified and documented.  I am uncertain how
Steven> your second category differs from the latter.

I've been doing several memory streamlining.  Often times I find myself
shutting down emacs, and restarting it, since I don't like having a >12M
process running around, when I only have 16megs (the only is sarcasm =) to
play with w/o swap.  I maintain a 20 meg swap space.

barebones emacs with my features.

USER       PID %CPU %MEM SIZE  RSS TTY STAT START   TIME COMMAND
dhall      264 11.3 15.0 1318 2240 pp0 T    21:41   0:01 emacs

  PID TTY MAJFLT MINFLT  TRS  DRS SIZE SWAP  RSS SHRD  LIB  DT COMMAND
  264 pp0    436    597 1472 1068 2540    0 2540 1720    0 203 emacs

my normal gnus reading news and mail (i decide to scrap VM in favour of
keeping with just one feature package to reduce memory usage, since each
have overhead associated with it).

USER       PID %CPU %MEM SIZE  RSS TTY STAT START   TIME COMMAND
dhall      214  3.4 31.8 6741 7748 v01 S    20:50   1:45 emacs -geometry 81x50

I normally try to keep my newsgroup access to below 300 articles, and I
still get this bloat.  My base emacs I have pretty much all non-essential
personal elisp hacks as autoloads, so I can forestall any memory usage till
the last possible second.

My normal free output
             total       used       free     shared    buffers
Mem:         14896      14640        256       5356       2068
- -/+ buffers:            12572       2324
Swap:        19968       4944      15024

I'm tempted to buy some more RAM, but as with most people in the PC
community, 16 megs is almost surely the "optimum".  And IMHO I've never
been one to go for the current software trend of "we've got the hardware,
why don't we abuse it?".  Are there any incorporated features I can do,
i.e. a list or possible ways to save memory?

d.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMSvZeYX26urqpgG1AQEyMQP/Z0jUZA1b9tj/DlCp6nwYRNlTVxB/SaEo
f54hAwpnc0unKYWEwAyjc3qrPXcvuqYN0qV68NXEVvSnOFdrvsQ21QHnPwVqCctI
fsmNt9wzw514nN7/5731aPQIpruc3avWn/BGGpK3MQ6zl/w4eVgmu4mltSUPLDF5
N23fRIl+oWI=
=Nihq
-----END PGP SIGNATURE-----
--
Dump:
  A Perl statement that is one of the many ways to get a Perl program
  to produce a core file.  Most of the other ones are undocumented.
                                ~ wall & schwartz, programming perl