Re: [go-cd] Go git repo has grown to 60k+ commits

2018-04-12 Thread 'Barry Greenwood' via go-cd
Hi I wouldn't expect the number of commits to cause that much of a performance hit. its more likely the issue is with the size of the XML document its self as it does a merge each time its edited that seems to give performance issues, I would suggest checking what is no longer used (eg

Re: [go-cd] Go git repo has grown to 60k+ commits

2018-03-21 Thread Gopal Singhal
Not really. But sometime it takes long to clone single file repo, or even annotate the file. Even gocd save changes from UI takes time. (Not very sure if that has some relation with Git history) Thanks, Gopal On Wed, Mar 21, 2018 at 5:09 PM, Ketan Padegaonkar < ketanpadegaon...@gmail.com>

Re: [go-cd] Go git repo has grown to 60k+ commits

2018-03-21 Thread Ketan Padegaonkar
Is a long commit history being a problem for you that you need it to be pruned out? Usually this should not be needed. On Wed, Mar 21, 2018 at 10:35 PM Gopal Singhal wrote: > Hi, > > Our Go servers git repo's commit history has grown to over 60k commits. Is > it

[go-cd] Go git repo has grown to 60k+ commits

2018-03-21 Thread Gopal Singhal
Hi, Our Go servers git repo's commit history has grown to over 60k commits. Is it possible to purge or flatten all the commits older than an year or so? Thanks, Gopal -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and