Better Git performance
While it is great the SSC supports Git, I have found that when connected to a large repository, SSC can take forever to commit or do a get latest.
I have also noticed that the working base and transient folders can grow quite large as the whole Git repo is cloned into these folders. I have had to periodically go in there and have Git compress it's objects so that I can reclaim some disk space.
I imagine that the performance of SSC is related to the size of the Git repo and I just feel like there is room for improvement in how SSC uses it's Git repos that could increase performance.
-
Peter commented
Also one option for a "fix" at least for our DBs, is that in a DB on 15K objects we've got filter rules that reduce the number greatly (maybe to only 100s). However it seems the comparison logic still looks at all objects, whereas it could easily cut its work by truly ignoring those objects filtered out at the onset.