GitUp hangs on almost every action with a repo about gitup HOT 10 OPEN

The snapshots mechanism is effectively how the undo/redo stack works in GitUp. We write up to a limit of I believe 100 past operations. So I wouldn't be surprised if over time you eventually get a slowdown when we are persisting up to 100 snapshots.

I know you said that you've only had this repo on your computer for a month, but is it a large repo that was cloned from elsewhere?

As for things that we could try to remedy the situation is have a configurable max number of snapshots to persist. Then you can still have the undo/redo benefits but with a smaller history. Any other solution would involve writing individual snapshots out rather than a single binary blob (most likely alternative), or having the write occur on a background thread (more difficult), but both of these options have a number of implications.

I'd be interested to see if in a week or so you experience the same problem.

from gitup.

This is unfortunately a long-standing issue #415. Frankly it's not one that I've actually investigated yet.

Does your performance improve if you delete that path (.git/co.gitup.mac/snapshots.data)?

from gitup.

Surprisingly it does, which is very interesting as the repo I use is rather new on my computer (about 1 month only).

from gitup.

Thank you for the explanation, yes, the repo is rather big, it was cloned directly from the server, but it has a lot of branches and tags.

I will get back in a week or so.

from gitup.

As we agreed, I am returning back with results. Delays on actions were gradually increasing during the week, so far the size of snapshots is about 500GB.

from gitup.

I've looked into the data and most of the plist contains references to tags:

from gitup.

500GB or MB? I certainly hope MB 😅. I think as an easy stopgap we could add a customization on the limit for snapshots, effectively limiting your undo stack. Otherwise I think it's a rework of the snapshot mechanism that frankly I don't have the time to maintain.

I think customizing the limit would allow you to use most of GitUp with easy. Out of curiosity if you browse snapshots (command-S) about how many would you say you have?

from gitup.

500MB, my bad (:

I have about 60 snapshots now, it is not much.

I have a question tho, why snapshot data contains information about all the tags? Most of them years old.

from gitup.

Ya, the problem is that the snapshots are exactly that, they are entire snapshots of the repo at a given time. So if you want to go back to the state of the repo yesterday, you can do that, but of course that means we need a way to get you there. Now of course a different approach that would be more efficient space wise is to have a diff of the repo, but I'm not sure of a practical way that can be done with what has been written so far.

If it is indeed tags that are really taking up the space for you, potentially git clone <repositoryUrl> --no-tags or deleting local tags git tag -d $(git tag -l) would improve the performance (though I assume you use tags yourself). You can also fetch a limited set of tags, but you have to then be careful as git fetch will pull down all tags at any given time. We could potentially have "limited snapshots" where we don't snapshot everything and allow the snapshots to be essentially sub-snapshots of the repo.

from gitup.

I'm not using the Snapshots feature at all, is it possible to make a product version without the snapshots, but that's super snappy?

from gitup.