ZODB Browser

BTree history is incomplete

Bug #474334 reported by Albertas Agejevas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ZODB Browser
Status tracked in Trunk
Trunk
Fix Released
High
Unassigned
ZODB Browser 0.5

Bug Description

The BTree history only displays the transactions that touched the BTree object itself, which is a rare occurence for large BTrees. Also, there is no way to browse the buckets that make up the tree.

Suggested fix: add an optional, slow, complete history for BTrees that would walk all the buckets and aggregate the changes.

Marius Gedminas (mgedmin)
Changed in zodbbrowser:
status: New → In Progress
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Will be fixed in version 0.5.

The complete history computation is not optional and cannot be turned off. If that turns out to be too slow in practice, something will have to be done about it.

Changed in zodbbrowser:
status: In Progress → Fix Committed
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Experiments show that an almost 2X speedup can be achieved by making sure we're not reloading the history/state of the same objects in the same request more than once.

Measured on a random OOBTree with 141 items and 67 revisions (oid=1105074 in a certain rather large Data.fs I have on my laptop), by running Zope under paster with keas.profile middleware: 6.366 seconds go down to 3.933 (numbers include cProfile overhead).

Marius Gedminas (mgedmin)
Changed in zodbbrowser:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.