KARL3

Relstorage trunk has significant RAM optimizations for packing

Bug #1302746 reported by Tres Seaver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL3
Fix Released
Low
Paul Everitt
KARL3 m141 "October 2014"
Tres Seaver (tseaver)
Changed in karl3:
importance: High → Medium
Paul Everitt (paul-agendaless)
Changed in karl3:
milestone: m136 → m138
Paul Everitt (paul-agendaless)
Changed in karl3:
importance: Medium → Low
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

We are quite unlikely to work on this in July.

Changed in karl3:
assignee: Tres Seaver (tseaver) → nobody
milestone: m138 → m139
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

The pain of huge database dump files is acute. However, the pain of: (a) re-awakening Shane to get a release, (b) absorbing the risk of a RelStorage rev, and then (c) all the work to actually run a pack is...

..higher than we are likely to do. Closing.

Changed in karl3:
milestone: m139 → m140
status: New → Won't Fix
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Re-opening as it appears we are going to get a new RelStorage release. If so, in October I can look at packing the database.

Changed in karl3:
assignee: nobody → Paul Everitt (paul-agendaless)
milestone: m140 → m141
status: Won't Fix → New
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Shane released an update. We are now using it.

Changed in karl3:
status: New → Fix Released
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.