Maybe that's your misconception then. The memory usage according to top is unlikely to go down significantly if at all. That's because the C-heap can not safely be shrunk most of the time. So I'd say forget the heap usage and watch them refcounts instead. Stefan On 5. Dez 2004, at 05:34, Andy Yates wrote:
Thanks for the explaination of how the transient gc works. That is exactly what I found when I looked in the source code and I can see all of this happening when I turn on the debug output. Sessions are created and placed in buckets. The active sessions move to the current bucket and expired session and old empty buckets get removed. Then there is a 1 in 6 chance they will be gc'ed on each request. I see all this happening but when the buckets are gc'ed the memory usage according to top does not go down.
-- The time has come to start talking about whether the emperor is as well dressed as we are supposed to think he is. /Pete McBreen/