# Is 5.2 Actually faster to close or is it just me?

**URL:** <https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973>\
**Category:** Development\
**Created:** [February 24, 2024, 5:48pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973 "2024-02-24T17:48:11Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mihle](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/mihle/32/612_2.png) [@Mihle](https://gramps.discourse.group/u/Mihle)\
**Post date:** [February 24, 2024, 5:48pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/1 "2024-02-24T17:48:11Z")

</div>

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”?

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [February 24, 2024, 5:54pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/2 "2024-02-24T17:54:42Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Mihle](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/mihle/32/612_2.png) [@Mihle](https://gramps.discourse.group/u/Mihle)\
**Post date:** [February 24, 2024, 6:19pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/4 "2024-02-24T18:19:08Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [February 24, 2024, 7:58pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/5 "2024-02-24T19:58:17Z")

</div>

> [@emyoulation](#):
>
> no change since the last backup.

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.

---

<div class="post-metadata">

**Author:** ![Mihle](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/mihle/32/612_2.png) [@Mihle](https://gramps.discourse.group/u/Mihle)\
**Post date:** [February 24, 2024, 8:28pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/6 "2024-02-24T20:28:33Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [February 24, 2024, 8:45pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/7 "2024-02-24T20:45:33Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Mihle](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/mihle/32/612_2.png) [@Mihle](https://gramps.discourse.group/u/Mihle)\
**Post date:** [February 24, 2024, 8:59pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/8 "2024-02-24T20:59:05Z")

</div>

I approve of speed improvements to Gramps a lot, I just wondered what the reason for it was, if its that, nice!

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [February 24, 2024, 9:24pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/9 "2024-02-24T21:24:34Z")

</div>

> [@Mihle](#):
>
> Less than 1-2 second, compared to 5.1.5 that used 5-10 sec to close (With no feedback it was closing)

A modal status popup was added in commit [b5e88c1](https://github.com/gramps-project/gramps/commit/b5e88c13f2094063f684149d250790dd45b9052b) to prevent the user closing Gramps during a backup.

The autobackup change is in commit [031325d](https://github.com/gramps-project/gramps/pull/1096/commits/031325d12806fdfcc56917207622c9c2d849b80a).

I can’t think of any other reason why Gramps would close faster. Possibly some updated library?

---

<div class="post-metadata">

**Author:** ![Mihle](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/mihle/32/612_2.png) [@Mihle](https://gramps.discourse.group/u/Mihle)\
**Post date:** [February 24, 2024, 9:46pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/10 "2024-02-24T21:46:51Z")

</div>

> [@Nick-Hall](#):
>
> A modal status popup was added in commit [b5e88c1](https://github.com/gramps-project/gramps/commit/b5e88c13f2094063f684149d250790dd45b9052b) to prevent the user closing Gramps during a backup.
> 
> The autobackup change is in commit [031325d](https://github.com/gramps-project/gramps/pull/1096/commits/031325d12806fdfcc56917207622c9c2d849b80a).
> 
> 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.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [February 24, 2024, 10:00pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/11 "2024-02-24T22:00:48Z")

</div>

Was thinking @dsblank had tweaked some things [based on an earlier thread](https://gramps.discourse.group/t/why-is-gramps-slow-in-some-places/4625)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\
**Post date:** [March 25, 2024, 10:01pm UTC](https://gramps.discourse.group/t/is-5-2-actually-faster-to-close-or-is-it-just-me/4973/12 "2024-03-25T22:01:04Z")

</div>

Closed on March 25, 2024, 10:01pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
