Skip to content
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.

Slow for large databases #12

Open
icemac opened this issue Mar 26, 2018 · 0 comments
Open

Slow for large databases #12

icemac opened this issue Mar 26, 2018 · 0 comments

Comments

@icemac
Copy link
Member

icemac commented Mar 26, 2018

@jimfulton wrote at 2018-03-25:

I think this is going to be prohibitively slow for large databases. The required downtime will be too long.
For automated fixups, I think it would be better to work at the pickle level. I'm thinking of a tool that converts individual pickles. (This might be useful for analysis as well.)
This would have a lot of advantages:

  • Potentially much faster because it doesn't require instantiating objects or running application-level code.
  • Doesn't require application classes to be around.
  • Can be integrated with existing workflows:
    • export/import
    • zodbcopy
    • ZRS replication.

I'll make a basic version of this that others can build on.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant