sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
wrote:
Is this to be expected because of the debugging code? I don't
seem to
remember that it's always been that way. If it's not, this is a
serious problem.
While it could be an XEmacs bug, it could also be memory-related:
* How much RAM do you have in your box?
* What's the size of the long-running XEmacs process?
* What are the values of `gc-cons-threshold' and `auto-gc-threshold'?
Basically, if your long-running XEmacs is swapping, or is doing many
gc's (your benchmark eats memory), it may not be surprising that the
long-running XEmacs takes longer.
On my old HP-UX workstation running 21.1.4 (yes, it's old), I get
the following:
Benchmark time GC's
Fresh XEmacs: ~11 sec 3
Old XEmacs (21 days): ~17 sec 3
I noticed, not surprisingly, that the gc's in the fresh XEmacs took
significantly less time.
However:
* I've got 256MB RAM.
* My long-running XEmacs is ~54MB in size. Everything fits into RAM.
* gc-cons-threshold is 4000000, and auto-gc-threshold is 1000000.
--
Darryl Okahata
darrylo(a)sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.