Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance/Speed #81

Open
wpccolorblind opened this issue Dec 11, 2017 · 1 comment
Open

Performance/Speed #81

wpccolorblind opened this issue Dec 11, 2017 · 1 comment

Comments

@wpccolorblind
Copy link

Hello -- first let me say this is an awesome tool and thanks for creating and updating this!

I'm wondering if you have a suggestion to speed up the computation and/or have plans to make this faster in the future.

I have a repo that has tens of thousands of commits from 30 different authors. I've git_stats running on this repo for many days (on my latest Mac Pro) and it's still going.

I tried subsetting to a commit range, which isnt seeming to have an effect (as in, it still looks like it's going to take a long long while). Here is my command line

git_stats generate --path= --out-path=./git_stats --first-commit-sha= --last-commit-sha=

I am seeing a different set of logs if I do and dont use the sha params. However, when I use the sha params i also get this error:

git show --shortstat --oneline --no-renames 268670637 -- .
fatal: Needed a single revision

I've double checked those sha ranges. That range is just 4 commits so I was hoping that would be fast.

Any ideas on all this?

@wpccolorblind
Copy link
Author

Update: the sha range command did just finish, it just took a lot longer than I would expect for analyzing 4 commits. Will try with a decently expanded range and see if it can finish in a reasonable amount of time...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant