On 2/16/2020 7:00 PM, Jakub Narebski wrote: > "Derrick Stolee via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > >> From: Derrick Stolee <dstolee@xxxxxxxxxxxxx> >> >> Use this max_changes option in the bloom filter calculations. This >> reduces the time taken to compute the filters for the Linux kernel >> repo from 2m50s to 2m35s. On a large internal repository with ~500 >> commits that perform tree-wide changes, the time reduced from >> 6m15s to 3m48s. > > I wonder if there is some large open-source project with many commits > performing tree-wide changes, that is with many commits with more than > 512 changed files with respect to the first parent. > > Maybe https://github.com/whosonfirst-data/whosonfirst-data-venue-us-ny > from "Top Ten Worst Repositories to host on GitHub - Git Merge 2017" > could be a good repository to test ;-) > Thanks for the suggestion! I will see if any of these repos gives us a good test bed and add the perf improvement numbers in the appropriate commit messages in v3. Cheers! Garima Singh
