Well, symptom was that it was called very often. like within minutes of the previous run (this was in >1GB processes).
/ David Hedbor
Previous text:
2003-01-12 18:25: Subject: GC improvement
I've also fixed some bugs in the old gc strategy:
o The decaying average calculation had a bug that caused the last reading (i.e. the last gc run) to be weighted very heavily. Thus a single "abnormal" gc run could cause the gc to schedule a fairly short or long gc interval the next time which might make it erratic.
o The aim for 20% garbage between gc runs was calculated on the wrong total amount of objects, so in effect the gc aimed for 16.7% instead. No big deal.
These bugs have been around at least since 0.6.
David, you've reported bad gc behavior. Could this explain your problems?
/ Martin Stjernholm, Roxen IS