On Friday 24 Feb 2012 16:55:23 Gwern Branwen wrote: > On Fri, Feb 24, 2012 at 2:44 AM, Peter Bienstman > > <[email protected]> wrote: > > That functionality is only planned for 2.1, I'm afraid, as I want to > > completely redesign the process to make it easier to share cards with > > media. > Exporting would presumably also save on disk space, would it not, if > it were used for the backups.
Not this kind of exporting, as that would just be for sharing cards and would leave the original database intact. > I just noticed that my backup folder takes up 333M for 10 backups at > ~33M a piece. In contrast, the 1.x default.mem weighs 9M, the gzipped > default.xml weighs 1.8M, and the 4 bzipped default.xmls in my 1.x > backup folder weigh 1.5M each or 5.8M total. Which is about 2 orders > of magnitude smaller, even if I had increased the kept backups to 10. It's not a fair comparison at all, because the 2.x db files also include the entire information of your 1.x history folder, in order to generate these nice stats :-) Anyway, what is on my post 2.0 TODO list is a feature to archive history older than X months to different file. The argument is not so much disk space (it's 2012 after all :-) ), but rather speed when syncing: the backup before sync take much, much longer that the actualy sync itself! I guess you know that you can change the number of backups kept in the config.py file. Cheers, Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
