Why does the git protocol create more objects than git-http-backend?

Question

I am using Git 1.7.1 configured with git-http-backend ( Smart HTTP ). I wanted to see how much faster this was matched with the git: // protocol, since now they should be level.

Turns off git: // the protocol compresses more objects (33.229 versus 21.193) for the exact same repo (even the trusted client side) and thus creates a batch file about 30 MB in size for my project.

Is there a reason why the git: // protocol requires more objects?

git: // Exit

 remote: Counting objects: 44510, done. remote: Compressing objects: 100% (33229/33229), done. Receiving objects: 100% (44510/44510), 124.07 MiB | 2.84 MiB/s, done. remote: Total 44510 (delta 22755), reused 15866 (delta 7516) Resolving deltas: 100% (22755/22755), done. 

http: // Exit

 remote: Counting objects: 24299, done. remote: Compressing objects: 100% (21931/21931), done. remote: Total 24299 (delta 7517), reused 0 (delta 0) Receiving objects: 100% (24299/24299), 95.95 MiB | 2.41 MiB/s, done. Resolving deltas: 100% (7517/7517), done. 

Answer 1

Maybe: through git you download files from all branches, and you can quickly switch between them, through http you download only the main branch.