At ITA we sometimes run with a dynamic heap of 1200 MB and more. (room) is the only problem I ever noticed but (room nil) works fine and provides the basic info I need to right-size all the spaces.
Side note and question: I noticed that I need a double-sized dynamic heap in this situation: - Lots of stuff in dynamic heap - save image with non(!)-purifying save - restart Lisp - lets say right after start I have 512 MB dynamic heap taken - I have to use -dynamic-space-size 1024 to get the Lisp started, otherwise I crash out on startup - once the REPL is up, I have the 512 MB It is not clear to me what is happening here. In a full copying GC it would be clear, but our gencgc shouldn't need twice the dynamic heap at any time, should it? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ No warranty. This email is probably produced by one of my cats stepping on the keys. No, I don't have an infinite number of cats.
