On Fri, Jul 12, 2013 at 10:23:34AM -0700, Junio C Hamano wrote: > Jeff King <p...@peff.net> writes: > > > The results for running (in linux.git): > > > > $ git rev-list --objects --all >objects > > $ git cat-file --batch-check='%(objectsize:disk)' <objects >/dev/null > > I can see how these patches are very logical avenue to grab only > on-disk footprint for large number of objects, but among the type, > payload size and on-disk footprint, I find it highly narrow niche > that a real user or script is interested _only_ in on-disk footprint > without even worrying about the type of object.
Yeah, I agree it is a bit of a niche. However, there are other code paths that might want only the size and not the type (e.g., we already know the object is a blob, but want to know size before deciding how to handle diff). But in general, I doubt the performance impact is a big deal there. It's only measurable when you're doing millions of objects. -Peff -- 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
