Architecture , db sanity etc: I have a few thoughts here: - its great to delete stuff we don't need - much of the stuff we have is only ours to look after; its really users data - the rest we can delete anytime we're happy that we won't need it (for debugging/legal reporting, whatever) - it would be nice to have a broad pattern of behaviour/interactions for cleaning up stuff that belongs to our users; some way of balancing the resources they are using/the benefits they get/the overhead to us of maintaining it.
Some things are ridiculously cheap to keep lots of, others are really very expensive. AIUI the big ones today are BranchRevision (An optimisation problem, we can address it transparently) and various rosetta tables. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
