🚀 go-pugleaf

System configuration:

6 mb   real memory   ~ 3 Mbytes available after UNIX
20+ mb virtual memory
UNIX SYS V   2.3.??
GNUemacs version 18.54.21 with loadst running and display-time


When a session has gotten big (on the order of an 8+ Mbyte process
size) and is allowed to sit overnight without being suspended, the
first keystroke in the morning causes RAMPANT paging.  An in-house
monitor shows that the GNUemacs process is paged in, and since there
is too little memory paged back out, until the entire image has been
paged through memory.  After this happens once, everything is alright
from then on.  Is there something that emacs could be searching for
throughout the entire process space?  Or, is there a bug in our paging
code that is simply freaking out at this point?  I cannot come up with
a reason for this strange behavior, and it can only be reproduced once
per day.


Mark Jones