Since I installed 5.2 to test it a little, I have noticed it closes way faster than 5.1.5 did for me Less than 1-2 second, compared to 5.1.5 that used 5-10 sec to close (With no feedback it was closing)
Is this because actual changes to 5.2, or is it because I installed it new and that somehow “refreshes” it, or something else that is on “my side”?
Did you have the previous version preferences set to backup on exit and this one isn’t?
Also, Backup is a bit smarter now. It does not backup upon exit if there was no change since the last backup.
Both are set to backup on exit, but backup only happens when there is actual changes. This speed difference is still noticeable to me even when just opening Gramps, looking at the tree, making no changes at all and therefore backup doesnt happen.
Sorry, this was probably inaccurate. Last Access timestamp is always changed.
So, the decision is probably based on there “not being any changes logged for Tree data in the Gramps session”. Changes to items not stored in the Tree (like current view, Active Person, or Preferences) won’t trigger a backup.
Did some testing and for me, neither 5.2 or 5.1.5 seem to make backup if there is no changes at all, 5.2 close faster for me than 5.1.5 in both cases, both when none of them create a new backup, or when both are (Just changed a event type back and fourth to test)
Well, there were performance assessments and optimization done too.
The expectation is that you will see Gramps do things much faster in some cases. (Deletes en masse, as an example.) Some major inefficiencies were fixed.
I approve of speed improvements to Gramps a lot, I just wondered what the reason for it was, if its that, nice!
A modal status popup was added in commit b5e88c1 to prevent the user closing Gramps during a backup.
The autobackup change is in commit 031325d.
I can’t think of any other reason why Gramps would close faster. Possibly some updated library?
Hm, maybe it partly just my 5.1.5 install that got some problems causing it to be slow and with 5.2 being new install fixed it then? I dont know.
Was thinking @dsblank had tweaked some things based on an earlier thread
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.