[ZCM] [ZC] 1314/ 2 Reject "ZODB size explosion"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1314 Update (Reject) "ZODB size explosion"
 Status Rejected, Database/bug critical
To followup, visit:
  http://zope.org/Collectors/Zope/1314

==============================================================
= Reject - Entry #2 by Caseman on May 5, 2004 9:58 am

 Status: Pending => Rejected

It is highly unlikely that this is a Zope bug. Given your description it is almost certainly due to one of the products you mentioned or your application's use of them. These types of problems are common in applications where database writes occur for read requests (which is generally a bad idea). 

Suggestion: Perform various read requests in your application, and check your undo log. If it contains entries for these requests, look to see where the database write is occuring.

I am rejecting this bug because I do not see evidence that the cause is Zope itself and not application or other third party code. If you can find further evidence to the contrary, feel free to reopen this issue.
________________________________________
= Request - Entry #1 by mtz on May 5, 2004 2:19 am


Uploaded:  "analyze_py_output"
 - http://zope.org/Collectors/Zope/1314/analyze_py_output/view
A strange problem where database size was originally about 6MB but after installing I18NLayer (first release 0.5.5, then CVS) and CMFBibliography (CVS HEAD) the db suddenly grew up to 300 MB. Packing returned it to about 35MB, but growth rate was not fixed, and trivial changes double or triple the size. Problem seems to be related to OOBTree.OOBucket and_IOBTree.IOBucket
taking most of the space (see below). 

==============================================================