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

Re: Git User's Survey 2008 partial summary, part 5 - other SCM

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 11, 2008, 22:05 UTC
Message-ID
<200809120005.34261.jnareb@gmail.com>
In-Reply-To
<48C98F92.40903@workspacewhiz.com>
Joshua Jensen wrote:
Show 17 quoted lines
> Anatol Pomozov wrote:
>> Jakub Narebski wrote:
>>>
>>> A bit suprising for me is high place of Perforce.
>>>     
>> Some huge companies use Perforce. A good example here is Google. But
>> at the same time there are a lot of Google employees who interested in
>> git. Especially after Linus TechTalk. Googlers created a wrapper for
>> perforce that tries to bring git to everyone and ~300 people actively
>> use it.
>>
> Many game companies use Perforce, as it has pretty good handling of 
> gigabytes upon gigabytes of art content.  This is one area where a 
> centralized repository trumps the distributed ones with full history.  
> The checkout tree for one product I worked on was 70 gigabytes, and I 
> still mapped out a large number of files.  You can imagine how that 
> becomes too unwieldy to have all history locally.

Dana How (Cc-ed) worked on better support in Git for very large and not well compressed files (and usually with short history). Her solution was to add support to git to limit size of blobs which entered packs (files/blobs of size larger than given limit were left as loose objects), and share those loose objects using network filesystem. You can search git mailing list to find exact details of this. IIRC mentioned patches were not accepted; instead there was proposed a solution where problematic blobs of very large files were packed into separate kept pack, and this kept pack (or packs, each containing single blob) were shared using some network filesystem (network drive).

In addition to that in Documentation/RelNotes-1.5.3 we have:
  - "pack-objects" honors "delta" attribute set in
    .gitattributes.  It does not attempt to deltify blobs that
    come from paths with delta attribute set to false.

(but as far as I can see this attribute is otherwise undocumented). This can also help performance for a repository with very large files.

-- 
Jakub Narebski
Poland
Previous: Jakub Narebski
Message 33 of 33 in “Git User's Survey 2008 partial summary”
  1. Jakub NarebskiSep 3, 2008
  2. Shawn O. PearceSep 3, 2008
  3. H.Merijn BrandSep 3, 2008
  4. Felipe ContrerasSep 3, 2008
  5. David AguilarSep 4, 2008
  6. Jan HudecSep 5, 2008
  7. David AguilarSep 6, 2008
  8. David BrownSep 3, 2008
  9. Scott ChaconSep 3, 2008
  10. Jakub NarebskiSep 3, 2008
  11. Jakub NarebskiSep 4, 2008
  12. Git User's Survey 2008 partial summary, part 3Jakub Narebski, Sep 6, 2008
  13. Shawn O. PearceSep 6, 2008
  14. Andreas EricssonSep 6, 2008
  15. Jonas FonsecaSep 7, 2008
  16. Shawn O. PearceSep 7, 2008
  17. Git User's Survey 2008 partial summary, part 4 - how do we use GitJakub Narebski, Sep 6, 2008
  18. Andreas EricssonSep 7, 2008
  19. Jakub NarebskiSep 7, 2008
  20. Git User's Survey 2008 partial summary, part 5 - other SCMJakub Narebski, Sep 11, 2008
  21. Anatol PomozovSep 11, 2008
  22. Jeff KingSep 11, 2008
  23. david@lang.hmSep 11, 2008
  24. Jakub NarebskiSep 12, 2008
  25. david@lang.hmSep 13, 2008
  26. Jakub NarebskiSep 13, 2008
  27. Mark BrownSep 15, 2008
  28. Nguyen Thai Ngoc DuySep 14, 2008
  29. Jakub NarebskiSep 14, 2008
  30. david@lang.hmSep 15, 2008
  31. Andreas EricssonSep 15, 2008
  32. Jakub NarebskiSep 16, 2008
  33. Jakub NarebskiSep 11, 2008

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.