It takes 5 minutes to index a new branch in git

If I'm reading it correctly, this has been running for 5 minutes on the stash repo on EAC: "/usr/bin/git whatchanged --always --reverse --date-order -m --no-abbrev -C --find-copies-harder 82cc50fc09c7e3cea29aa2134ba23904f8bb75c2 --pretty=format:C:%H%nP:%P%nA:%aN%nE:%aE%nR:%cN%nF:%cE%nD:%at%nS:%s%nB:%b%n@@fe_body_end@@"
https://extranet.atlassian.com/crucible/admin/admin.do#repositories-view-stash
ah just finished
335451ms though

====

It appears that whenever you push a new branch/tag in the Stash repo, FishEye now needs > 5 minutes to catch up.
I just pushed a new branch with a single new changeset
/usr/bin/git whatchanged --always --reverse --date-order -m --no-abbrev -C --find-copies-harder 7a5884dae370371bd4467cc7be0da8c82f9f8818 --pretty=format:C:%H%nP:%P%nA:%aN%nE:%aE%nR:%cN%nF:%cE%nD:%at%nS:%s%nB:%b%n@@fe_body_end@@"
Michael Heemskerk
Jun-14 9:15 AM
The issue is that this command calculates the manifest changes for ALL commits. FishEye then goes and discards all but one of the returned commits
an easy fix is to add excludes to the command to exclude any commits that are already know:
/usr/bin/git whatchanged --always --reverse --date-order -m --no-abbrev -C --find-copies-harder 7a5884dae370371bd4467cc7be0da8c82f9f8818 ^master ^1.1 --pretty=format:C:%H%nP:%P%nA:%aN%nE:%aE%nR:%cN%nF:%cE%nD:%at%nS:%s%nB:%b%n@@fe_body_end@@"
on my local box that brings down the time for the whatchanged command from 4 minutes to 0.03s