On 9/6/07, Jon Smirl <jonsmirl@xxxxxxxxx> wrote: > Use blame for an example. Blame has to crawl every commit to see if it Sure. Build a quick dedicated index for that and measure - cost (size and commit/fetch costs) - benefit - frequency of usage git is a special-purpouse DB that does great for certain access patterns. Have a look at monotone for a design that looks a lot like git but is backed by a general purpouse DB and does equally poorly for all access patterns ;-) > It keeps doing this until it figures out the last > author for every line in the file. Worse case blame has to crawl every > commit in the data store. Yep. Can we get a minimal-cost index with just enough hints that can speed up blame, and perhaps git log with/very/deep/path? Probably! That's worth pursuing sure. martin - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
