[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawlXt6nnNs-3uw61EGYtxr_AVhJqXybwLR8"
 nickname="Bruno"
 subject="comment 2"
 date="2015-04-15T17:51:18Z"
 content="""
@CandyAngel Thank you for your **git annex find** tips. But for git gc, it seem not working fine :)
After i have executed the **git gc**, the **git annex info** return the result after **1h 45m**

    % time git annex info
    repository mode: indirect
    trusted repositories: 0
    semitrusted repositories: 5
	00000000-0000-0000-0000-000000000001 -- web
 	00000000-0000-0000-0000-000000000002 -- bittorrent
 	181d4dae-2131-435e-9c00-b8c7f1bfc332 -- [sbackup]
 	2db1f8e7-0b29-4d61-8875-a4a4a42a79dd -- [dellcomputer]
 	703df355-73a6-4487-97fd-a3a5d6ae034e -- usbhomebackup [here]
    untrusted repositories: 0
    transfers in progress: none
    available local disk space: 135.24 gigabytes (+1 megabyte reserved)
    local annex keys: 275416
    local annex size: 780.55 gigabytes
    annexed files in working tree: 265888
    size of annexed files in working tree: 751.49 gigabytes
    bloom filter size: 16 mebibytes (55.1% full)
    backend usage: 
	SHA256E: 541304

git annex info  83,95s user 50,68s system 2% **cpu 1:45:01,70 total**


Can you explain exactly the git gc or git repack parameters that you use for optimizing git annex performance  ?

Thanks

"""]]
