Hi Developers, As you may have noticed (if you run "git clone" frequently), a simple clone of our DSpace/DSpace GitHub is seemingly getting slower and slower:
git clone g...@github.com:DSpace/DSpace.git At last check, even with my relatively speedy internet connection, it's taking about 3-5 minutes. This isn't so horrible, but it's not the speediest clone either. Essentially, from my investigations, the problem is that we have a ton of old binary files (old JARs, PDFs) in our Git history which is causing our repo to be rather large in size. Most of these binary files were carried over from SVN. I've opened a ticket to discuss this problem: https://jira.duraspace.org/browse/DS-1750 From my calculations (see the ticket comments), our existing repo is 132MB in size. However, if we were to purge these binary JARs & PDFs from our Git history, it would shrink our repo to just *32MB* in size. Obviously, purging files from Git history would affect *everyone*. So, we shouldn't take this action lightly (if we want to even do it). But, I wanted to start this discussion to see what others think, and start to determine whether we feel it is worth the pain, or not. - Tim -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
