git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git clone: very long "resolving deltas" phase

From
VBVitaly Berov <vitaly.berov@gmail.com>
Date
Apr 6, 2010, 15:56 UTC
Message-ID
<v2qecffb261004060856qcb769a06vf40ad2a75a3aa4fd@mail.gmail.com>
In-Reply-To
<q2mec874dac1004060850r5eaa41fak2ba9889d07794651@mail.gmail.com>

Why does git compute checksums on the client side? Isn't it already calculated on the "server" side?

2010/4/6 Shawn Pearce <spearce@spearce.org>:
Show 32 quoted lines
> Nope, the resolving deltas phase is about computing the checksums of each
> object on the client side of the connection.  Repacking the server might
> have little impact on this phase, other than maybe to reduce the size and
> thus the disk io required to scan the entire pack.
>
> On Apr 6, 2010 9:32 AM, "Andreas Ericsson" <ae@op5.se> wrote:
>> On 04/06/2010 05:29 PM, Vitaly wrote:
>>> I didn't try this, but I'll give it a try, thanks.
>>>
>>> And what does this stage mean?
>>>
>>
>> It means the server is busy creating a packfile to send
>> over the wire. If you pack the repository before cloning
>> from it, deltas from the packfile will simply be copied
>> into the new pack. This will provide a huge speedboost,
>> so make sure to repack the repository on the server every
>> once in a while.
>>
>> --
>> Andreas Ericsson andreas.ericsson@op5.se
>> OP5 AB www.op5.se
>> Tel: +46 8-230225 Fax: +46 8-230231
>>
>> Considering the successes of the wars on alcohol, poverty, drugs and
>> terror, I think we should give some serious thought to declaring war
>> on peace.
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Previous: VitalyNext: Nicolas Pitre
Message 22 of 39 in “git clone: very long "resolving deltas" phase”
  1. Vitaly BerovApr 6, 2010
  2. Matthieu MoyApr 6, 2010
  3. Vitaly BerovApr 6, 2010
  4. VitalyApr 6, 2010
  5. Andreas EricssonApr 6, 2010
  6. Nicolas PitreApr 6, 2010
  7. Marat RadchenkoApr 7, 2010
  8. Nicolas PitreApr 7, 2010
  9. Nicolas PitreApr 6, 2010
  10. Nicolas PitreApr 6, 2010
  11. VitalyApr 7, 2010
  12. Nicolas PitreApr 7, 2010
  13. Vitaly BerovApr 9, 2010
  14. Matthieu MoyApr 9, 2010
  15. Nicolas PitreApr 9, 2010
  16. Vitaly BerovApr 10, 2010
  17. Nicolas PitreApr 9, 2010
  18. Vitaly BerovApr 10, 2010
  19. Vitaly BerovApr 10, 2010
  20. Nicolas PitreApr 11, 2010
  21. VitalyApr 12, 2010
  22. Vitaly BerovApr 6, 2010
  23. Nicolas PitreApr 6, 2010
  24. Vitaly BerovApr 7, 2010
  25. Ilari LiusvaaraApr 7, 2010
  26. VitalyApr 7, 2010
  27. Ilari LiusvaaraApr 7, 2010
  28. Jakub NarebskiApr 7, 2010
  29. Nicolas PitreApr 7, 2010
  30. VitalyApr 7, 2010
  31. Nicolas PitreApr 7, 2010
  32. Vitaly BerovApr 9, 2010
  33. Nicolas PitreApr 9, 2010
  34. Vitaly BerovApr 10, 2010
  35. Nicolas PitreApr 7, 2010
  36. Sverre RabbelierApr 7, 2010
  37. VitalyApr 7, 2010
  38. VitalyApr 7, 2010
  39. Nicolas PitreApr 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.