AW: [Zope-dev] Zope 2.7 memory behaviour
Arndt Droullier
ad at dvelectric.com
Mon Mar 22 14:55:04 EST 2004
Your debug information looks like severel objects referenced by
acquisition remain in memory.
You can be sure this is the case if you in the management interface to
Control Panel/Database Management/main/Flush Cache
and remove all objects from cache. If the reference count doesn´t change
then some objects are leaking.
The reference count is the number in the table, or in other words you
have 18136 Acquisition.ImplicitAcquirerWrapper objects in memory. This
value should normally be much less after flushing the cache.
BTW, the effect I described is no real problem. After some time the
memory usage gets stable.
Greetings, Arndt.
>The debug information looks rather strange to me, but I don't know
>anything about internals of Zope. Anyway I have here reference counts
>going up fast. Don't know whether this is normal or not.
>
>Class March 22, 2004 5:26 pm March 22, 2004 5:38 pm Delta
>Acquisition.ImplicitAcquirerWrapper 850 18136 +17286
>ZPublisher.HTTPRequest.HTTPRequest 145 3026 +2881
>ZServer.HTTPResponse.ZServerHTTPResponse 139 3019 +2880
>ZPublisher.BaseRequest.RequestContainer 135 3015 +2880
>DateTime.DateTime.DateTime 51 52 +1
>
>I'll let you know, should I find some solution (apart from restarting :-)).
____________
Virus checked by G DATA AntiVirusKit
Version: AVK 14.0.298 from 27.01.2004
Virus news: www.antiviruslab.com
More information about the Zope-Dev
mailing list