-----Original Message----- On Feb 20, 2015 1:58AM Martin Fick wrote: >On Feb 19, 2015 5:42 PM, David Turner <dtur...@twopensource.com> wrote: > > This one is not affected by how deep your repo's history is, or how > > wide your tree is, so should be quick.. >Good to hear that others are starting to experiment with solutions to this >problem! I hope to hear more updates on this.
<snip-snip> Now that Jojo and I have git 2.3.0 ported to the HP NonStop platform, there are some very large code bases out there that may start being managed using git. These will tend to initially shallow histories (100's not 1000's of commits, and fairly linear) but large source and binaries - I know of a few where just the distributed set of sources are above 1Gb and are unlikely to be managed in multiple repos despite my previous best efforts to change that. Fortunately, It is a relatively simple matter to profile the code on the platform for various operations so data on where to improve may be available - I hope. With that said, for NonStop file system tends to be heavier weight than on Linux (many more moving parts by virtue of the MPP nature of the OS and hardware). Packing up changes seems pretty good, but any operating involving creating a large number of small files does hurt a bunch. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
