-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alex and I are volunteers doing this work for a non-profit, so any
ideas or "yep, that's normal, live with it" would be greatly
appreciated! (If the latter answer, I would still like to better
understand where that memory is being used; I still don't understand
how it could be the object cache, which is often cited as the main
cause of memory creep).
You would need to study all the inefficiencies inherent in the
content types you use, or all the nasty stuff that gets pulled in
for viewing the site furniture shown for every page etc. Very few
product authors out there put memory efficiency onto their priority
list.
P.S.: Memory is cheap. Cheap enough even for a non-profit. Go get
some, or at least compare the cost of buying meory with the cost of
countless hours you already have and may continue to spend on this.
I'm not saying it's not a worthwhile task to try and get to the
bottom of code inefficiencies, but keep the practical side in mind.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFF4W+WRAx5nvEhZLIRAq5tAKCCB16LWniHD5lZuAO8cLmn7oeMZACbBTAn
aH0XuUuNyOY63pvT7j47+cA=
=pN7N
-----END PGP SIGNATURE-----
_______________________________________________
Zope maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
