orbvoc.dbow3 is a ~50mb file that is checked into the repo. Since a git clone pulls all commits, every version of this file is pulled upon a clone. Currently there are 2 commits of this file, so a clone is >100MB. Every time you change this file and push (even if is a single byte change), the repo will bump up by another 50MB. Is this what you want? It would be preferable to use git lfs or git annex to add this file to the repo.
orbvoc.dbow3 is a ~50mb file that is checked into the repo. Since a git clone pulls all commits, every version of this file is pulled upon a clone. Currently there are 2 commits of this file, so a clone is >100MB. Every time you change this file and push (even if is a single byte change), the repo will bump up by another 50MB. Is this what you want? It would be preferable to use git lfs or git annex to add this file to the repo.
Unfortunately, even if you were to remove this file from the repo, that 100MB is still in the history so will come along with every clone. To get rid of it, you have to do some extra work. See http://stackoverflow.com/questions/2100907/how-to-remove-delete-a-large-file-from-commit-history-in-git-repository or https://git-scm.com/book/en/v2/Git-Internals-Maintenance-and-Data-Recovery#Removing-Objects